JDK-6231214 : os::malloc() should fail more gracefully
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2005-02-19
  • Updated: 2010-08-06
  • Resolved: 2005-05-30
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 6
6Resolved
Related Reports
Duplicate :  
JDK-4965918 - JVM Out of Memory Handling: print extra information to help application team
Description
Many JVM crashes reported by customers have been traced down to running the machine out of swap space or available address space. One type of failure that can easily and should be fixed is the situation where os::malloc() is about to return NULL. There are many code paths through the JVM (handle allocation being one recently encountered) which call malloc() and expect a non-NULL result, and if malloc() fails for any reason the JVM will crash at a random point. We should at least add code to os::malloc() to check for a NULL return value and call vm_exit_out_of_memory() or similar to produce an error log indicating the cause of the crash.

6223676 is a recent occurrence of this problem. It is probably related to 4719004 but is not exactly the same.

###@###.### 2005-2-19 02:30:54 GMT