JDK-8224983 : Cleanup G1 locking during nmethod removal during code cache unloading
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 13
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2019-05-29
  • Updated: 2019-05-29
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8224875 - Shenandoah: ParallelCleaning code unloading should take lock to protect shared code roots array
Description
JDK-8224875 showed that G1 uses some ugly MutexLocker trick (using NULL as mutex in some cases) to do proper locking when doing nmethod removal during code cache unloading.

Try to remove the need for passing NULL in the MutexLocker to make the code less surprising.