G1 does not always scan CLDG references to the old gen potentially causing problems with eager reclaim

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P3
    • tbd
    • Affects Version/s: 9
    • Component/s: hotspot
    • gc

      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.

            Assignee:
            Unassigned
            Reporter:
            Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: