JDK-6188718 : File.deleteOnExit() - "Clean up and return" after JNU_ThrowOutOfMemoryError
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.2_05
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2004-11-01
  • Updated: 2010-08-06
  • Resolved: 2005-10-29
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 b59Fixed
Related Reports
Relates :  
JDK-4513817 - File.deleteOnExit consumes memory
Relates :  
JDK-6271145 - "Clean up and return" after JNU_ThrowOutOfMemoryError
Description
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.
###@###.### 11/1/04 15:54 GMT
Comments
SUGGESTED FIX Appears to be just an oversight in this function: after the JNU_ThrowOutOfMemoryError we need to return. ###@###.### 11/1/04 12:26 GMT
01-11-2004
EVALUATION A return must be inserted after JNU_....., reassigning the bug to the for further evaluation and fix. ###@###.### 2005-04-06 21:08:44 GMT For File.deleteOnExit, we should add the return as indicated above. I've filed bug 6271145 to cover the reported AWT issues. ###@###.### 2005-05-16 21:22:09 GMT
01-11-2004