You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ant.apache.org by bu...@apache.org on 2009/09/01 16:56:31 UTC

DO NOT REPLY [Bug 45439] Memory growth during copy with use of FilterReader

https://issues.apache.org/bugzilla/show_bug.cgi?id=45439


Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |1.8.0


--- Comment #1 from Stefan Bodewig <bo...@apache.org> 2009-09-01 07:56:29 PDT ---
I think svn revision 810080 fixes the memory leak in a clean way - except when
something prior to returning the reader in ChainReaderHelper throws an
exception, that is.

If you <typedef> or <componentdef> your filterreader and don't use the
<filterreader classname="..."> syntax only a single instance will be used to
copy all files, which should avoid the problem in 1.7.x altogether.

Regarding your hack: it would be safer to perform your action in an overridden
close method (which basically is what my patch does at the chain level).

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.