JDK-8075229 : G1 does not always scan CLDG references to the old gen potentially causing problems with eager reclaim
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-03-16
  • Updated: 2019-02-11
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8027959 - Early reclamation of large objects in G1
Description
G1 does not actually scan all roots during a young gc (not all metadata for example). So if we ever have metadata (from metaspace) pointing directly to humongous object in the java heap we're screwed, because eager reclaim may just remove that object.

(This is due to the assumption that old gen data is not moved during young-only gcs)

Add some verification code for this case.
Comments
There may not be any kind of metadata that points to a humongous (type) array; this potential problem came up during discussing another issue and was considered worth noting here.
16-03-2015
Preliminary ILW: I: high -> crash L: low -> not known to occur W: med -> disable eager reclaim -> P3
16-03-2015