| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8047264 | 8u25 | Bengt Rutisson | P2 | Resolved | Fixed | b03 |
| JDK-8044625 | 8u20 | Bengt Rutisson | P2 | Closed | Fixed | b19 |
| JDK-8053388 | emb-8u26 | Bengt Rutisson | P2 | Resolved | Fixed | b17 |
The fix for JDK-8029255 removed the post barrier for setting the next field of Reference objects.
http://hg.openjdk.java.net/jdk9/hs-gc/hotspot/rev/fbc1677398c0
That post barrier dirtied a lot of cards that didn't really have to be dirty, but it saved us from other missed card marks. See for exampleJDK-8031703.
When running the Stress BPM another case of a missing barrier was detected.
The missing barrier occurs when we prune the discovered list in G1 and the list contains reference objects that are in different old regions.
http://hg.openjdk.java.net/jdk9/hs-gc/hotspot/rev/fbc1677398c0
That post barrier dirtied a lot of cards that didn't really have to be dirty, but it saved us from other missed card marks. See for example
When running the Stress BPM another case of a missing barrier was detected.
The missing barrier occurs when we prune the discovered list in G1 and the list contains reference objects that are in different old regions.
- backported by
-
JDK-8047264 G1: Missing post barrier in processing of j.l.ref.Reference objects
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-8029255 G1: Reference processing should not enqueue references on the shared SATB queue
-
- Resolved
-