JDK-8235247 : WorkerDataArray leaks C heap memory for associated work items
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 12,13,14
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-12-03
- Updated: 2020-01-31
- Resolved: 2019-12-04
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 14 |
|---|
14 b26Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Integer work items are not freed at deletion of a WorkerDataArray. This is problematic for weak reference processing via WeakProcessor::weak_oops_do() as it provides a temporary WeakProcessorPhaseTimes object, leaking a few 100 bytes per GC.
Comments
|