commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DIGESTER-125) Memory leak in Digester class by inputSources collection
Date Mon, 09 Jun 2008 15:03:45 GMT

     [ https://issues.apache.org/jira/browse/DIGESTER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Simon Kitching resolved DIGESTER-125.
-------------------------------------

    Resolution: Fixed

Thanks for pointing this out. The cleanup method has been modified to now clear the inputSources
list (svn commit r665710).

Note, however, that reusing a Digester instance is not recommended. See the wiki FAQ:
   http://wiki.apache.org/commons/Digester/FAQ

I'll add some info about that to the Digester class javadocs.

> Memory leak in Digester class by inputSources collection 
> ---------------------------------------------------------
>
>                 Key: DIGESTER-125
>                 URL: https://issues.apache.org/jira/browse/DIGESTER-125
>             Project: Commons Digester
>          Issue Type: Bug
>    Affects Versions: 1.8
>            Reporter: Andrey Polyakov
>             Fix For: 1.8.1
>
>
> There is no clean method for inputSources list from Digeste class, 
> in frequent usage of parse() method inputSources collection will collect references to
sources objects. In this situation the number of object references represented by sources
from inputSources,
> will be increased and consume a lot of memory. For intensive parsing smth around 200
mb for 8 hours was consumed.
> Solution is simple method cleanup() should contain line inputSources.clear(); at the
end of the method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message