JDK-8196716 : Refactor Cleaner Registration to avoid resource leak
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 11
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2018-02-02
  • Updated: 2018-09-11
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-8195059 - Update java.net Socket and DatagramSocket implementations to use Cleaner
Description
Cleaner registration typically occurs after resources have already been allocated; if an exception occurs before/during the registration of the cleanable the resource may not be freed.
Consider if registration should provide a callback to open the resource after the Cleanable instance has been allocated.
Also previously mentioned during finalization removal in zip.

http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-February/051277.html