commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Forrest Girouard <>
Subject Re: native memory leak on every call to File.deleteOnExit()
Date Thu, 04 Mar 2004 02:30:11 GMT

On Mar 3, 2004, at 6:18 PM, Noel J. Bergman wrote:

>>>> Is any one on this list aware that every call to File.deleteOnExit()
>>>> leaks memory in the native heap?
>>> I am.  Code intended for server use should be audited to remove that
>>> call.
>> I wasn't aware that there were any expectations in this area.  Can
>> you explain further?
> See the bug parade.  I suspect I know whose quotes are there 
> explaining the
> problem.

I'm well aware of bug id 4513817 
but inferred perhaps incorrectly from your comment that there is a 
well-known process under which Jakarta components must be handled in 
order to be used in a server setting.

>>> If someone wants to create an alternative using phantom
>>> references, that would be fine, and generally useful.
>> I know what phantom references are in theory but I've not yet used 
>> them
>> personally.  Can you give me any further information on how this might
>> be done?
> See: 
> for
> an intro to PhantomeReferences.

Like I said I know what PhantomReferences are I just wanted to know how 
you thought they might be most effectively employed for the issue at 

> If no one gets to this, I might hack a TemporaryFile class, but I've 
> got
> higher priority items on my plate at the moment.

In case it's not obvious nothing has higher priority for me at the 
moment, I'm on this 24/7 until I have a work around and/or solution.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message