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

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2014/04/02 12:25:15 UTC

[jira] [Updated] (CONFIGURATION-572) Possible memory leak when using CombinedConfiguration

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

Sebb updated CONFIGURATION-572:
-------------------------------

    Summary: Possible memory leak when using CombinedConfiguration  (was: Possibe memory leak when using CombinedConfiguration)

> 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
>         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)