JDK-8245925 : G1 allocates EDEN region after CDS has executed GC
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 12,13,14,15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-05-27
- Updated: 2024-10-16
- Resolved: 2020-06-14
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 16 |
|---|
16 b02Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
During the development for JDK-8244778, I encountered this assert: http://hg.openjdk.java.net/jdk/jdk/file/ca1687338afe/src/hotspot/share/gc/g1/g1HeapVerifier.cpp#l337 assert(!cl.has_unexpected_holes(), "all holes should have been caused by humongous regions"); During -Xshare:dump, we would force a GC, http://hg.openjdk.java.net/jdk/jdk/file/ca1687338afe/src/hotspot/share/memory/metaspaceShared.cpp#l1870 Usually this will clear the EDEN region, leaving the top of the heap unused. Here's the log from java -Xshare:dump -Xlog:gc*=info,gc+region=trace,gc+alloc+region=debug (see attached good.txt) [4.742s][info ][cds ] Dumping symbol table ... [4.812s][info ][gc,region,cds ] HeapRegion 0x00000003d2000000 OLD [4.812s][info ][gc,region,cds ] HeapRegion 0x00000003d2800000 FREE [4.812s][info ][gc,region,cds ] HeapRegion 0x00000003d3000000 FREE [4.812s][info ][gc,region,cds ] HeapRegion 0x00000003d3800000 FREE [4.812s][info ][cds ] Dumping objects to closed archive heap region ... However, when the bug happens, we see an EDEN region at the top of the heap, which CDS doesn't want to see: (see attached bad.txt) [1.370s][info ][cds ] Dumping symbol table ... [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080000000 OLD [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080100000 OLD [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080200000 FREE [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080300000 FREE [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080400000 FREE [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080500000 FREE [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080600000 FREE [1.387s][info ][gc,region,cds ] HeapRegion 0x0000000080700000 EDEN hole **** unexpected **** [1.387s][warning][gc,verify ] All free regions should be at the top end of the heap, but we found holes. This is probably caused by (unmovable) humongous allocations, and may lead to fragmentation while writing archive heap memory regions. [1.388s][info ][cds ] Dumping objects to closed archive heap region ...
Comments
|