Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F05110413 for ; Tue, 29 Apr 2014 16:42:18 +0000 (UTC) Received: (qmail 8593 invoked by uid 500); 29 Apr 2014 16:42:16 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 8511 invoked by uid 500); 29 Apr 2014 16:42:16 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 8483 invoked by uid 99); 29 Apr 2014 16:42:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Apr 2014 16:42:15 +0000 Date: Tue, 29 Apr 2014 16:42:15 +0000 (UTC) From: "Joe Littlejohn (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CURATOR-105) Memory leak when using service providers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)