curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Littlejohn (JIRA)" <>
Subject [jira] [Commented] (CURATOR-105) Memory leak when using PathChildrenCache
Date Tue, 13 May 2014 13:00:23 GMT


Joe Littlejohn commented on CURATOR-105:

Thanks for investigating this Jordan. Do you think this is a simple one to fix? I see you're
targeting 2.5.0 for this, I know this is an unfair question but do you have any ballpark estimate
for when you'd like 2.5.0 to ship? :)

> Memory leak when using PathChildrenCache
> ----------------------------------------
>                 Key: CURATOR-105
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework, Recipes
>    Affects Versions: 2.4.1, 2.4.2
>         Environment: Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
>            Reporter: Joe Littlejohn
>            Assignee: Jordan Zimmerman
>              Labels: discovery
>             Fix For: 2.5.0
>         Attachments:
> 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:

This message was sent by Atlassian JIRA

View raw message