curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Littlejohn (JIRA)" <>
Subject [jira] [Created] (CURATOR-240) Severe memory leak in TreeCache when path does not exist
Date Fri, 31 Jul 2015 13:26:04 GMT
Joe Littlejohn created CURATOR-240:

             Summary: Severe memory leak in TreeCache when path does not exist
                 Key: CURATOR-240
             Project: Apache Curator
          Issue Type: Bug
          Components: Recipes
    Affects Versions: 2.8.0
         Environment: java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

OSX Yosemite
            Reporter: Joe Littlejohn
            Priority: Critical

When creating a TreeCache, if the path supplied does not exist in Zookeeper then the heap
is quickly exhausted. The problem appears to be instances of org.apache.curator.framework.imps.NamespaceWatcher.

Try running the following test:

import org.apache.curator.framework.CuratorFramework;
import org.apache.curator.framework.CuratorFrameworkFactory;
import org.apache.curator.retry.RetryOneTime;
import org.apache.curator.test.TestingServer;

public class TreeCacheLeak {

    public static void main(String[] args) throws Exception {

        TestingServer server = new TestingServer();
        final CuratorFramework curatorFramework = CuratorFrameworkFactory.newClient(server.getConnectString(),
new RetryOneTime(1));

        final TreeCache cache = new TreeCache(curatorFramework, "/foo/bar/baz");

        try {
            while (true) {
        } finally {


Launch the class then connect e.g. jvisualvm. You'll see the heap growing and if you watch
for a few minutes then take a heap dump, you'll see millions of instances of org.apache.curator.framework.imps.NamespaceWatcher
are present.

This message was sent by Atlassian JIRA

View raw message