commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Forrest Girouard <Forrest.Girou...@openwave.com>
Subject Re: native memory leak on every call to File.deleteOnExit()
Date Thu, 04 Mar 2004 01:20:59 GMT

On Mar 3, 2004, at 4:42 PM, Tomasz Pik wrote:

> Forrest Girouard wrote:
>
>> On Mar 3, 2004, at 4:05 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.
>> Ok.  I wasn't aware that there were any expectations in this area.  
>> Can you explain further?  Is there other calls that need to be 
>> "removed" for server use?
>
> If you're asking about Java libraries, not directly commons libraries
> I know two examples, that cause problems with webapp classloaders
> and reloading: adding SecurityProviders and loading native libraries.

Thanks for the input although I'm aware of the issues surrounding these 
two examples.  By the way, we completely avoid all the native code 
issues of which there are many by simply having a local surrogate 
process make those calls on our behalf.

Cheers,
	Forrest


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message