Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8192647

GClocker induced GCs can starve threads requiring memory leading to OOME

    XMLWordPrintable

Details

    • gc

    Description

      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

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JDK-8205628 vmTestbase/gc/lock/jni/jnilock003/TestDescription.java fails with java.lang.OutOfMemoryError: Java heap space

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JDK-8222715 vmTestbase/gc/lock/jni/jnilock001/TestDescription.java timeout after test passed

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8226536 Catch OOM from deopt that fails rematerializing objects

          • P2 - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8048556 Unnecessary GCLocker-initiated young GCs

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8137099 G1 needs to "upgrade" GC within the safepoint if it can't allocate during that safepoint to avoid OoME

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8308507 G1: GClocker induced GCs can starve threads requiring memory leading to OOME

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-8319881 G1: Investigate thread starvation during G1CollectedHeap::attempt_allocation_slow.

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Enhancement - null JDK-7129164 JNI Get/ReleasePrimitiveArrayCritical don't scale

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-8236594 G1: Provide object pinning

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Enhancement - null JDK-8233280 Remove GCLockerInvokesConcurrent

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Enhancement - null JDK-8228964 Improve G1 GCLocker allocation stall

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              iwalulya Ivan Walulya
              tschatzl Thomas Schatzl
              Votes:
              1 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated: