curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <>
Subject [jira] [Commented] (CURATOR-14) Memory leak in Curator watches
Date Thu, 02 May 2013 11:24:16 GMT


Ioannis Canellos commented on CURATOR-14:

I tried the suggested approach about caching watchers and it seems to work. The only problem
is providing a working equals() and hashCode() for the Watchers implemented as anonymous inner
classes. So I think that something like a CacheableWatcher that could provide an impl of these
two based on a key property could reduce the boilerplate.

If no one is already working on it I could provide a patch.
> Memory leak in Curator watches
> ------------------------------
>                 Key: CURATOR-14
>                 URL:
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Recipes
>    Affects Versions: 2.0.0
>            Reporter: Brandon Beck
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>         Attachments:
> The JVM runs out of memory if you repetitively create a PathChildrenCache, start it then
immediately stop it.  It appears that the memory is taken up by a watch that isn't ever cleaned
up.  Curator attempts to do some pooling of watches, but doesn't seem to use the path in the

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message