commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomasz Pik <pi...@ais.pl>
Subject Re: native memory leak on every call to File.deleteOnExit()
Date Thu, 04 Mar 2004 00:42:02 GMT
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.

Regards,
Tomek

>     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