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.
(This is due to the assumption that old gen data is not moved during young-only gcs)
Add some verification code for this case.
- relates to
-
JDK-8027959 Early reclamation of large objects in G1
-
- Resolved
-