-
Bug
-
Resolution: Fixed
-
P2
-
12, 13, 14
-
b26
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.
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.
- relates to
-
JDK-8235347 [Backout] 8235247: WorkerDataArray leaks C heap memory for associated work items
-
- Resolved
-
-
JDK-8235341 Improve WorkerDataArray API to disallow separate instantiation of sub-items
-
- Resolved
-
-
JDK-8235346 [Redo] 8235247: WorkerDataArray leaks C heap memory for associated work items
-
- Closed
-
-
JDK-8072498 Multi-thread JNI weak reference processing
-
- Resolved
-