NPG: Audit usage of Heap_lock for allocations from Metaspaces

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • 8
    • Affects Version/s: 8
    • Component/s: hotspot
    • None
    • gc
    • generic
    • generic

      With the permanent generation allocations from the perm gen were guarded with
      the Heap_lock. Allocations in Metaspaces (replacement for perm gen) are protected by
      per Metaspace locks. Removing the use of the Heap_lock here previously caused
      problems. Check if there is still a need for the Heap_lock and, if so, why is it
      needed.

            Assignee:
            Unassigned
            Reporter:
            Jon Masamitsu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: