JDK-6271145 : "Clean up and return" after JNU_ThrowOutOfMemoryError
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-05-16
  • Updated: 2012-01-11
  • Resolved: 2006-03-04
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
6 b75Fixed
Related Reports
Relates :  
JDK-6188718 - File.deleteOnExit() - "Clean up and return" after JNU_ThrowOutOfMemoryError
Description
This bug breaks out the awt portions reported in bug 6188718.  All fields from that bug have been duplicated here where applicable.

Native JVM support routines make calls to JNU_ThrowOutOfMemoryError,
e.g. when a malloc has failed.

They must not then go on to assume the Throw... does not return. 
e.g. do not use the value that came back from the failed malloc.

###@###.### 2005-05-16 21:20:19 GMT
Comments
SUGGESTED FIX Appears to be just an oversight in this function: after the JNU_ThrowOutOfMemoryError we need to return. ###@###.### 2005-05-16 21:20:20 GMT
16-05-2005
EVALUATION Using values after failed calloc in awt_init_display() is dangerous. Should fix. ###@###.### 2005-05-17 11:54:13 GMT
16-05-2005