JDK-7049999 : G1: Make the G1PrintHeapRegions output consistent and complete
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs22
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-05-31
- Updated: 2013-09-18
- Resolved: 2011-09-30
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | Other |
|---|---|---|
7u2Fixed  |
8Fixed |
hs22Fixed |
Description
The G1PrintHeapRegions parameter generates a trace of which regions are allocated and which are collected. It'd be nice if we are able to "replay" the region allocation / reclamation based on such a trace. However, currently we are unable to as the trace is incomplete. These are the reasons why: - There is no information on which regions are reclaimed during cleanup. - There is no humongous region alocation information. - After a full compaction, the heap is drastically restructured all the information of regions that were allocated up to that point is invalidated. In addition we should make the output more consistent than it is now.
Comments
|