JDK-8251455 : OopStorage usage rules should be documented and checked
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-08-11
  • Updated: 2020-08-12
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-8251336 - OopHandle release can not be called in a safepoint
Description
JDK-8251336 showed that recent code changes to use OopStorage were flawed because the release operation could be carried out whilst a safepoint were active.

As [~rkennke] noted:

In general, non-GC threads should not mess with GC roots (e.g.
OopStorage) during safepoints. I don't think that this plays well with
any GC. Not sure if it can be automatically detected, it sure would be
nice if that would fire an assert or so.