| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2208961 | 7 | John Cuthbertson | P3 | Closed | Fixed | b138 |
| JDK-2206999 | 6u25 | John Cuthbertson | P3 | Closed | Fixed | b03 |
| JDK-2208480 | hs21 | John Cuthbertson | P3 | Closed | Fixed | b08 |
The issue that is causing the failures seen in 7009266 arise as a result of performing reference discovery during concurrent marking, followed by processing any discovered references at the end of concurrent marking.
By partially removing the fix for 6994628 we can eliminate the disovery of reference objects during concurrent marking - the code that traces objects in concurrent marking will treat reference objects as regular objects and mark through them (marking the referent object and any object that is reachable from it).
By marking the referent objects means that the Logger objects in the KitchenSink bigapp will always be strongly reachable and marked.
By partially removing the fix for 6994628 we can eliminate the disovery of reference objects during concurrent marking - the code that traces objects in concurrent marking will treat reference objects as regular objects and mark through them (marking the referent object and any object that is reachable from it).
By marking the referent objects means that the Logger objects in the KitchenSink bigapp will always be strongly reachable and marked.
- backported by
-
JDK-2206999 G1: Partially remove fix for 6994628
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JDK-7023785 G1: SIGSEGV in G1ParCopyHelper::copy_to_survivor_space(oopDesc*)
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
(1 relates to)