JDK-6469791 : JVM crash if it is not enough space for object heap
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2006-09-12
  • Updated: 2012-02-01
  • Resolved: 2010-09-02
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 7
7Resolved
Related Reports
Duplicate :  
Description
Running the nsk.stress suite on machine with low free space we get many FAILs with:
#Error occurred during initialization of VM
#Could not reserve enough space for object heap

But some of tests from nsk/stress/jck12a nsk/stress/jck60:
(Removed test names to prevent fail_list)

completed with the crash.
We got it on em64t-001.sfbay, but it looks like this is not platform depended problem.

Comments
EVALUATION The message: Error occurred during initialization of VM Could not reserve enough space for object heap Isn't a crash. Maybe it used to be. There are several problems that this bug seems to be referring to, which are documented in other bugs: 6859079: JNI_CreateJavaVM() terminates the process on error condition instead of returning error code This bug reports that we should return JNI_ENOMEM for this "Could not reserve enough space for object heap" We also have: 6302804: Hotspot VM dies ungraceful death when C heap is exhausted in various places. whose title says it all. This bug appears to be either fixed if it's complaining about crashing, or a duplicate of one of the above. I'll pick 6859079.
02-09-2010