JDK-8210155 : Lock ClassLoaderDataGraph
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 12
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-08-29
  • Updated: 2019-02-24
  • Resolved: 2018-08-31
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 12
12 b10Fixed
Related Reports
Relates :  
JDK-8210422 - runtime/modules/ModuleStress/ExportModuleStressTest.java - assertion failed: address not aligned: 0x00000008baadbabe
Relates :  
JDK-8219621 - G1 concurrent class unloading is disabled during high class loading activity
Description
Add lock to ClassLoaderDataGraph in preparation for concurrent class unloading.

New entries in the singly linked list ClassLoaderDataGraph are added via CAS.  There is no performance reason to do this.  It was done to be careful about safepointing while installing ClassLoaderData, but GC will find the CLD through the class loader oop.

There is various CLDG walking through the VM which now need to either take the lock or be at a safepoint.