JDK-7176269 : NPG: Audit usage of Heap_lock for allocations from Metaspaces
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2012-06-12
  • Updated: 2012-10-10
  • Resolved: 2012-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Duplicate :  
JDK-6964458 - Reimplement class meta-data storage to use native memory
Description
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.
Comments
EVALUATION I removed the Heap_lock from metadata allocation when doing the CompressedKlassPointers code.
05-09-2012