You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <ji...@apache.org> on 2006/11/14 22:36:39 UTC
[jira] Updated: (GERONIMO-1464) Avoid use of file.deleteOnExit() -
will cause allocation of 1K of memory per call until JVM terminates
[ http://issues.apache.org/jira/browse/GERONIMO-1464?page=all ]
Matt Hogstrom updated GERONIMO-1464:
------------------------------------
Fix Version/s: Wish List
(was: 1.2)
Moving out for a later version.
> Avoid use of file.deleteOnExit() - will cause allocation of 1K of memory per call until JVM terminates
> ------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-1464
> URL: http://issues.apache.org/jira/browse/GERONIMO-1464
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Memory Leaks
> Affects Versions: 1.0
> Reporter: John Sisson
> Priority: Minor
> Fix For: Wish List
>
>
> I haven't run into a memory problem but came across this bug in Sun's bug database and a number of people warning not to use deleteOnExit() in server code.
> According to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4513817 each call to file.deleteOnExit() will allocate 1K of memory until the JVM terminates. I have not had the chance to verify it, but I have raised this JIRA in case someone is tracking a memory leak in the future or someone has time to review our usage of deleteOnExit().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira