[
https://issues.apache.org/jira/browse/CONFIGURATION-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-572.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Fixed in SVN in revision 1590418. Thanks for the report and the patch.
> Possible memory leak when using CombinedConfiguration
> -----------------------------------------------------
>
> Key: CONFIGURATION-572
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-572
> Project: Commons Configuration
> Issue Type: Bug
> Reporter: Rob Walker
> Priority: Minor
> Fix For: 2.0
>
> Attachments: 2960.patch
>
>
> We altered our code to use CombinedConfiguration in a more dynamic way and
> immediately started to see large memory usage. Looking for a potential leak,
> we realised we were missing a clear() when the config objects were done with.
> Even with this call in, the leak persisted. It seems that whilst the clear()
> method cleans up the object, it doesn't clear the listener list as well. This
> leaves around stale references which then never become GC.
> Will attach the patch we found worked at curing this
--
This message was sent by Atlassian JIRA
(v6.2#6252)
