Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2177193 | 7 | Y. Ramakrishna | P3 | Closed | Fixed | b34 |
JDK-2170226 | 6u12 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-2169513 | 6u7-rev | Yumin Qi | P3 | Resolved | Fixed | b15 |
JDK-2174432 | 5.0u19 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-2166041 | 5.0u18-rev | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b03 |
JDK-2174450 | 1.4.2_21 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-2179173 | 1.4.2_20-rev | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b04 |
JDK-2166040 | 1.4.2_19-rev | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b09 |
JDK-2166206 | hs11 | Poonam Bajaj Parhar | P2 | Resolved | Fixed | b17 |
JDK-2169512 | hs10 | Yumin Qi | P3 | Resolved | Fixed | b27 |
this problem was first diagnosed:
What we were doing is that if we overflowed the marking stack
when trying to push a newly marked (now grey) object encountered during
precleaning, we would just dirty the card the object (now marked)
lay on, with the expectation that a later precleaning pass or the final
remark phase (which would pick up all remaining dirty cards) would deal
with the object. But of course in the case of an object _array_,
preclean/remark would just scrub the dirty pages not the entire array,
so the part of the object array that protruded off the dirtied page
on to a possibly clean page would not be scanned and if that part
contained references to white objects, those would be lost.
The fix of course is in the case of overflown object arrays,
to dirty all the pages that the newly marked overflown object array
lies on when encoding its greyness for the purposes of rescan (by a
later preclean pass or the subsequent final remark).
- backported by
-
JDK-2166206 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2166040 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2166041 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2169512 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2169513 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2170226 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2174432 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2174450 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2179173 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Resolved
-
JDK-2177193 CMS: Incorrect encoding of overflown object arrays during concurrent precleaning
- Closed
- relates to
-
JDK-6578335 CMS: BigApps failure with -XX:CMSInitiatingOccupancyFraction=1 -XX:+CMSMarkStackOverflowALot ...
- Closed
-
JDK-6681372 64-bit VM CompilerThread received SEGV in ciObjectFactory::find_non_perm()
- Closed
-
JDK-6697967 Java core file from Global Server prdgc01a --- 64-bit java process
- Closed
-
JDK-6752632 (audit) apply HSX-11 fix for 6722112 to HSX-12 and HSX-13
- Closed