-
Bug
-
Resolution: Won't Fix
-
P3
-
9, 10, 11, 14, 16, 17, 20, 21
Threads may be starved from receiving memory by the GClocker. This typically leads to OOME in the affected threads. This works as follows:
1. Thread A tries to allocate memory as normal, and tries to start a GC; the GCLocker is active and so the thread gets stalled waiting for the GC
2. GCLocker induced GC executes and frees some memory
3. Thread A does not get any of that memory, but other threads also waiting for memory.
4. Goto 1 until the gclocker retry count has been reached
1. Thread A tries to allocate memory as normal, and tries to start a GC; the GCLocker is active and so the thread gets stalled waiting for the GC
2. GCLocker induced GC executes and frees some memory
3. Thread A does not get any of that memory, but other threads also waiting for memory.
4. Goto 1 until the gclocker retry count has been reached
- relates to
-
JDK-8192647 GClocker induced GCs can starve threads requiring memory leading to OOME
- Open
- links to
-
Review openjdk/jdk/14077