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

Improve how JNIHandleBlock::oops_do distinguishes oops from non-oops

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 14
    • Fix Version/s: 14
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b10

      Description

      In JNIHandleBlock::oops_do(), the blocks may contain free list next pointers or oops. The distinction is detected by asking the CollectedHeap if the pointer value is in the heap reserve or not.

      This forces GCs to have one single contiguous heap reservation, without holes in it, which seems like an unnecessary restriction.

        Attachments

          Activity

            People

            Assignee:
            eosterlund Erik Ă–sterlund
            Reporter:
            eosterlund Erik Ă–sterlund
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: