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

Posted to dev@curator.apache.org by "Brandon Beck (JIRA)" <ji...@apache.org> on 2013/04/09 00:46:18 UTC

[jira] [Updated] (CURATOR-14) Memory leak in Curator watches

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

Brandon Beck updated CURATOR-14:
--------------------------------

    Attachment: MemoryTest.java

With this test I can reliable run out of memory (8mb heap) in a minute or so.
                
> Memory leak in Curator watches
> ------------------------------
>
>                 Key: CURATOR-14
>                 URL: https://issues.apache.org/jira/browse/CURATOR-14
>             Project: Apache Curator
>          Issue Type: Bug
>            Reporter: Brandon Beck
>            Assignee: Jordan Zimmerman
>         Attachments: MemoryTest.java
>
>
> 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 pooling.

--
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: http://www.atlassian.com/software/jira