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

G1 eager reclaim card dirtying may dirty outside of allocated objects

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • Resolved In Build:
      b94

      Description

      A stale remembered set entry on a humongous region selected for eager reclaim may point to unallocated memory.
      Previously a fix was applied to avoid dirtying cards which cover regions which are free but this fix is in fact insufficient, we also need to consider the case where a region is not full.
      This can lead to verification failures in fastdebug builds.

      Suggested fix is to change the check from "not is free" to "is in closed subset".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mgerdin Mikael Gerdin (Inactive)
                Reporter:
                mgerdin Mikael Gerdin (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: