Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8075229

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

    Details

    • Type: Enhancement
    • Status: Open
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: 9
    • Fix Version/s: tbd
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: