-
Bug
-
Resolution: Fixed
-
P2
-
hs17, hs18
-
b02
-
generic
-
generic
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2191240 | 7 | Tony Printezis | P2 | Resolved | Fixed | b88 |
JDK-2197990 | 6u23 | Tony Printezis | P2 | Resolved | Fixed | b01 |
JDK-2199940 | 6u22m | Tony Printezis | P2 | Resolved | Fixed | b01 |
JDK-2193593 | 6u21p | Tony Printezis | P2 | Resolved | Fixed | b03 |
JDK-2191028 | 6u21 | Tony Printezis | P2 | Resolved | Fixed | b02 |
JDK-2191029 | hs17 | Tony Printezis | P2 | Closed | Fixed | b12 |
We have investigating marking issues in G1 as part of 6666145 and this is the one that's causing the most failures. See the Evaluation of that CR for a bit more info.
- backported by
-
JDK-2191028 G1: threads created during marking do not active their SATB queues
- Resolved
-
JDK-2191240 G1: threads created during marking do not active their SATB queues
- Resolved
-
JDK-2193593 G1: threads created during marking do not active their SATB queues
- Resolved
-
JDK-2197990 G1: threads created during marking do not active their SATB queues
- Resolved
-
JDK-2199940 G1: threads created during marking do not active their SATB queues
- Resolved
-
JDK-2191029 G1: threads created during marking do not active their SATB queues
- Closed
- relates to
-
JDK-6666145 G1: marking verification fails
- Closed
-
JDK-6867250 G1: java.lang.ArrayIndexOutOfBoundsException in Win64
- Closed
-
JDK-6980838 G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue
- Closed