Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2208959 | 7 | Tony Printezis | P4 | Closed | Fixed | b138 |
When G1 tries to do a humongous allocation but cannot find enough contiguous regions in the heap it will attempt to do a collection pause in case this pause reclaims enough contiguous space for the allocation to succeed. Currently, the attempt to do a collection pause does not check whether the GC locker is active or not and, if it's active, it will keep attempting to do back-to-back collection pauses which will be unsuccessful. Instead, it should stall until the GC locker becomes inactive.
- backported by
-
JDK-2208959 G1: humongous allocation attempts should take the GC locker into account
-
- Closed
-
- relates to
-
JDK-7033292 G1: nightly failure: Non-dirty cards in region that should be dirty
-
- Closed
-
-
JDK-7005799 G1: nsk/regression/b6186200 fails with OOME
-
- Closed
-