| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2198045 | 7 | Tony Printezis | P3 | Closed | Fixed | b109 |
| JDK-2197840 | 6u23 | Tony Printezis | P3 | Resolved | Fixed | b01 |
| JDK-2199740 | 6u22m | Tony Printezis | P3 | Resolved | Fixed | b01 |
| JDK-2197549 | 6u21p | Tony Printezis | P3 | Resolved | Fixed | b03 |
During testing some other changes, I came across a case where humongous objects were being allocated on young regions and copied during collection pauses. This breaks the fundamental G1 assumption that humongous objects are always allocated separately. I've only seen this when running dacapo pmd.
- backported by
-
JDK-2197549 G1: sometimes humongous objects are allocated in young regions
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-