Move the ChunkManager instances out of the VirtualSpaceLists

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P2
    • hs25
    • Affects Version/s: hs25
    • Component/s: hotspot
    • gc
    • b52
    • Not verified

        In the fix for 'JDK-8024547: MaxMetaspaceSize should limit the committed memory used by the metaspaces' we need to make a clearer distinction between when new memory is committed and when memory is allocated inside already committed memory.

        Moving the ChunkManager, which handles the free chunk list, out of the VirtualSpaceList, which handles the committed metaspace memory, is a step in that direction.

              Assignee:
              Stefan Karlsson
              Reporter:
              Stefan Karlsson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: