JDK-8221643 : Tighten up assert(_keep_alive >= 0) in CLD::inc_keep_alive
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-03-28
- Updated: 2019-04-16
- Resolved: 2019-03-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.
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 13 |
|---|
13 b15Fixed  |
Related Reports
|
Relates :
|
Description
The assertion implies the possible transition _keep_alive = 0 -> _keep_alive = 1, which has implication to GC. Based on comments in JDK-8162553, it was done this way due to null class loader data having a _keep_alive value of 0. However, we now set null class loader data's _keep_alive = 1 in ClassLoaderData's constructor, so above case should not happen. Let's tighten the assertion to avoid confusion.