-
Bug
-
Resolution: Unresolved
-
P3
-
9, 10, 11, 14, 16, 17, 20, 21, 22, 23
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
- duplicates
-
JDK-8205628 vmTestbase/gc/lock/jni/jnilock003/TestDescription.java fails with java.lang.OutOfMemoryError: Java heap space
- Closed
-
JDK-8222715 vmTestbase/gc/lock/jni/jnilock001/TestDescription.java timeout after test passed
- Closed
- relates to
-
JDK-8229120 Intermittent gc/stress/gclocker/TestExcessGCLockerCollections.java test failures
- Open
-
JDK-8226536 Catch OOM from deopt that fails rematerializing objects
- Resolved
-
JDK-8048556 Unnecessary GCLocker-initiated young GCs
- Resolved
-
JDK-8137099 G1 needs to "upgrade" GC within the safepoint if it can't allocate during that safepoint to avoid OoME
- Resolved
-
JDK-8308507 G1: GClocker induced GCs can starve threads requiring memory leading to OOME
- Closed
-
JDK-8319881 G1: Investigate thread starvation during G1CollectedHeap::attempt_allocation_slow.
- Open
-
JDK-7129164 JNI Get/ReleasePrimitiveArrayCritical don't scale
- Resolved
-
JDK-8236594 G1: Provide object pinning
- Closed
-
JDK-8233280 Remove GCLockerInvokesConcurrent
- Resolved
-
JDK-8228964 Improve G1 GCLocker allocation stall
- Closed