JDK-8033542 : test/java/util/logging/SimpleLogManager might let Loggers be gc'ed too early.
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.logging
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-02-04
- Updated: 2016-06-13
- Resolved: 2014-02-05
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.
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 8 | JDK 9 |
|---|---|
8u20Fixed  |
9 b03Fixed |
Related Reports
|
Relates :
|
Description
SimpleLogManager extends CustomLogManager which keeps strong references on loggers added to the LogManager. However the logger passed by SimpleLogManager to CustomLogManager is not the logger originally created - and therefore there may not be any strong references kept on the original logger.