[
https://issues.apache.org/jira/browse/CURATOR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Littlejohn updated CURATOR-105:
-----------------------------------
Attachment: ServiceCacheLeakTest.java
Run against a Zookeeper instance with a service registered to see the heap
grow. I've been unable to replicate the same problem when using the
TestingServer.
> Memory leak when using service providers
> ----------------------------------------
>
> Key: CURATOR-105
> URL: https://issues.apache.org/jira/browse/CURATOR-105
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 2.4.1, 2.4.2
> Environment: Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
> Reporter: Joe Littlejohn
> Labels: discovery
> Attachments: ServiceCacheLeakTest.java
>
>
> I've observed a memory leak in our production system using Curator service
> discovery.
> If you run the attached test case and watch the process with jvisualvm you'll
> see that the heap grows and grows as the test is running. Taking a heap dump
> will reveal thousands of ServiceInstance and ServiceCacheImpl instances that
> are retained even though the provider is closed after each usage. The
> references appear to be traced back to the PathChildrenCache. This appears to
> be a leak that shouldn't occur if the provider is correctly closed each time.
> There is also a heap dump available here:
> https://dl.dropboxusercontent.com/u/10909453/heapdump-curator-leak.hprof.tar.gz
--
This message was sent by Atlassian JIRA
(v6.2#6252)
