-
Bug
-
Resolution: Unresolved
-
P4
-
19, 20, 21, 22, 23, 24, repo-loom
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
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:
- duplicates
-
JDK-8285417 [LOOM] vmTestbase/nsk/jdi/VMOutOfMemoryException times out on windows
- Closed
-
JDK-8321700 Test vmTestbase/nsk/jdi/ReferenceType/instances/instances004/TestDescription.java failed with OutOfMemoryError
- Closed
-
JDK-8322644 JDI ReferenceType/instances/instances004 timed out
- Closed
-
JDK-8346583 vmTestbase/nsk/jdi/stress/serial/mixed002/ fails with OOME, timeout, and broken pipe
- Closed