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

ConcurrentLocksDump::dump_at_safepoint() should tolerate Out-of-memory conditions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 11
    • hotspot
    • None
    • svc

      ConcurrentLocksDump::dump_at_safepoint() creates a GrowableArray to hold the found AbstractOwnableSynchronizer instances, but if allocation (or growing?) of the array causes an OOM condition then it will abort the VM - vm_exit_out_of_memory.

      Diagnostic tools, that may be being used to diagnose excessive memory use should not themselves cause an abort due to OOM.

      The code needs to be aware of OOM possibility and deal with it accordingly.

            Unassigned Unassigned
            dholmes David Holmes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: