JDK-8234020 : Remove FullGCCount_lock
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-11-12
- Updated: 2021-05-04
- Resolved: 2021-04-27
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 17 |
|---|
17 b20Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
After the removal of CMS (JDK-8229049) and the introduction of G1OldGCCount_lock (JDK-8232588), the FullGCCount_lock looks vestigial. It is locked and notified by the two overloads of GenCollectedHeap::update_full_collections_completed. The 1-arg overload is no longer called (it was only called by CMS). And there are no waits, so the notification is useless. Since SerialGC is the only collector still using GenCollectedHeap, the locking in the 0-arg overload isn't needed. Doing those cleanups would leave it unused.
Comments
|