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

Tests that trigger OOME can fail due to triggering an inadvertent OOME on an IO poller thread

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 19, 20, 21, 22, 23, 24, repo-loom
    • core-svc

      A number of debugger tests that force an OOME are seeing failures due to communication issues with the debuggee. There is evidence that during the brief period where the debuggee has caused an out of memory, an IO poller thread (needed by virtual threads blocked on IO) is also getting an OOME, and then no longer functions. Once this happens, read or writes by the debuggee can fail (timeout).

      Failed tests include:

      vmTestbase/nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001/VMOutOfMemoryException001.java
      vmTestbase/nsk/jdi/stress/serial/mixed002/TestDescription.java
      vmTestbase/nsk/jdi/ReferenceType/instances/instances004/TestDescription.java

      Previously filed CRs include:

      JDK-8285417 - [LOOM] vmTestbase/nsk/jdi/VMOutOfMemoryException times out on windows
      JDK-8346583 - vmTestbase/nsk/jdi/stress/serial/mixed002/ fails with OOME, timeout, and broken pipe
      JDK-8322644 - JDI ReferenceType/instances/instances004 timed out
      JDK-8321700 - Test vmTestbase/nsk/jdi/ReferenceType/instances/instances004/TestDescription.java failed with OutOfMemoryError

            Unassigned Unassigned
            cjplummer Chris Plummer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: