JDK-8177915 : Clarify Reference.reachabilityFence use
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-03-31
  • Updated: 2024-06-08
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
Duplicate :  
JDK-8191002 - Arrays.fill() in finalizer mangles newly allocated array in another thread
Duplicate :  
JDK-8191002 - Arrays.fill() in finalizer mangles newly allocated array in another thread
Relates :  
JDK-8314480 - Memory ordering spec updates in java.lang.ref
Relates :  
JDK-8149610 - (ref) Reference construction vs referent lifetime races
Relates :  
JDK-8133348 - Reference.reachabilityFence
Description
The description and use recommendations in Reference.reachabilityFence need some improvements.

Refer to the openjdk email: related to deprecation of Object.finalize.

http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-March/047035.html
Comments
Reassigning this to [~bchristi], who just did a big java.lang.ref update in JDK-8314480 that also modified reachabilityFence. Not sure there's anything left to do in this bug report, given that Hans commented several times on JDK-8314480. So maybe this is a duplicate of that. If it's not a duplicate, the clarifications suggested here should be made more explicit.
08-06-2024
Added interested parties to the Watcher list.
31-03-2017