Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083124 | emb-9 | Thomas Schatzl | P4 | Resolved | Fixed | b37 |
JDK-8086442 | 8u65 | Thomas Schatzl | P4 | Resolved | Fixed | b01 |
JDK-8075811 | 8u60 | Thomas Schatzl | P4 | Resolved | Fixed | b09 |
JDK-8137588 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8077457 | emb-8u60 | Thomas Schatzl | P4 | Resolved | Fixed | team |
However, it only does so when there is at least one humongous object candidate. This is problematic since this makes getting further information about humongous objects somewhat unreliable.
The problem is that early in the GC phase, we check whether there are any candidates, and if not, skip the actual humongous reclaim phase (because there is nothing that can be reclaimed).
It would be preferable that if G1TraceReclaimDeadHumongousObjectsAtYoungGC is set, do not skip the humongous reclaim phase even if it cannot reclaim anything, but at least print the information.
Also, add humongous object size to the output.
This would help analyzing for
- backported by
-
JDK-8075811 G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
-
- Resolved
-
-
JDK-8077457 G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
-
- Resolved
-
-
JDK-8083124 G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
-
- Resolved
-
-
JDK-8086442 G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
-
- Resolved
-
-
JDK-8137588 G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object
-
- Resolved
-
- relates to
-
JDK-8048179 Early reclaim of large objects that are referenced by a few objects
-
- Resolved
-
-
JDK-8048180 Investigate early reclaim of large reference arrays
-
- Open
-