JDK-6867617 : VMOutOfMemoryException001 fails with parallel GC
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 6u21,6u23,7,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,linux,solaris
  • CPU: generic
  • Submitted: 2009-07-31
  • Updated: 2014-12-09
  • Resolved: 2014-12-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b05Fixed
Related Reports
Relates :  
Description
The following VM/NSK test:

    nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001

continues to fail in Parallel GC, but with a different failure
mode than 6729714.

http://sqeweb.sfbay.sun.com/nfs/tools/gtee/results/JDK7/NIGHTLY/VM/2009-07-30/GC_Baseline-XXParallel/vm/solaris-i586/client/mixed/solaris-i586_client_mixed_nsk.quick-jdi.testlist/ResultDir/VMOutOfMemoryException001/VMOutOfMemoryException001.log

[2009-07-31T07:16:46.56] binder> Launching debugee
[2009-07-31T07:16:46.56] binder> Waiting for VM initialized
[2009-07-31T07:16:50.75] Initial VMStartEvent received: VMStartEvent in thread main
[2009-07-31T07:16:50.75] debugee.stderr> Debuggee nsk.share.jdi.AbstractJDIDebuggee : sending the command: ready
[2009-07-31T07:16:50.75] Got expected exception: com.sun.jdi.VMOutOfMemoryException
[2009-07-31T07:16:50.75] # ERROR: TEST FAILED: debuggee's process finished with status: 1
[2009-07-31T07:16:50.75] TEST FAILED


The exit status of 1 indicates an ungraceful termination due
to an out of memory condition. My search showed failures
like this on Solaris X86, Solaris AMD64, and Solaris SPARC

Comments
RULE nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001 ExitCode 97
17-10-2014

Fix pushed. I will close this bug when test is stable in nightly. http://vmsqe-app.ru.oracle.com/hg/sqe/vm/9/ws_int_spb/vm/rev/0c4833fee30c
17-10-2014

The debugger will allocate memory in the debuggee until it gets a VMOutOfMemoryError. The purpose of this is just to verify that VMOutOfMemoryErrors are generated. But since we allocate memory in the debuggee until it gets an OOM, we sometimes also get an OutOfMemoryError in the debuggee. The default debuggee considers this as an error and the test fails. Proposed fix is just to ignore any OOM in the debuggee, since they are quite expected.
15-10-2014

I can not reproduce this with parallel GC, but with G1GC it failes every time.
15-10-2014