[CURATOR-105] Memory leak when using PathChildrenCache

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1, 2.4.2
• Fix Version/s: 2.5.0
• Component/s: Framework, Recipes
• Labels: discovery
• Environment: Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
• Assignee: Jordan Zimmerman
• Reporter: Joe Littlejohn
• Created: 29/Apr/14 16:38
• Updated: 23/May/14 15:08
• Resolved: 23/May/14 15:08

Description

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