Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EC99D984 for ; Sat, 13 Oct 2012 01:39:16 +0000 (UTC) Received: (qmail 83442 invoked by uid 500); 13 Oct 2012 01:39:15 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 83404 invoked by uid 500); 13 Oct 2012 01:39:15 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 83396 invoked by uid 99); 13 Oct 2012 01:39:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Oct 2012 01:39:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Oct 2012 01:39:09 +0000 Received: by mail-wi0-f180.google.com with SMTP id hm4so98409wib.15 for ; Fri, 12 Oct 2012 18:38:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WafBpQGJu9sOM7QqlKD8sCYQfX2QcdDZQsAKMor0i9I=; b=jMuyI9viyxCPPfQ3Dy6VYhsBpjf/Avtx0EQ7ykCFpymSPHWfzNKR7YQnEBrjFFd0/1 3+QUUglaL5CzNIvyMCs17kDAZmsFpybLo3oJuqOCde1FF95XXZ7kc9QU15ASwcJooNeO b4ic/P3lsI54iPxsrWUiJ8gwTS9Q8z1Jb+3R1bFqVOmEKrAad/Yc/HIdn93rM5kcuXYr beREvMIjDjJBYoynON4MwGVTxfQS2uwaKn8LLy8VMfdpczAavI3UQYWfD+mdH6k9Vngk 9+4VTmVcFHRW82ukFPi50/KNfMVHgMCOd7Ophpd+qANL8APkIM/N4DBxnJ/y7wXoOF8F JsDg== Received: by 10.180.89.7 with SMTP id bk7mr9678945wib.0.1350092329214; Fri, 12 Oct 2012 18:38:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.72.200 with HTTP; Fri, 12 Oct 2012 18:38:19 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Fri, 12 Oct 2012 18:38:19 -0700 Message-ID: Subject: Re: Memory leaks in zoo_multi API To: user@zookeeper.apache.org Cc: michi@cs.stanford.edu Content-Type: multipart/alternative; boundary=f46d04447e73b262b904cbe6dd31 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04447e73b262b904cbe6dd31 Content-Type: text/plain; charset=UTF-8 Can you provide sample code and more detailed replication instructions? On Fri, Oct 12, 2012 at 6:06 PM, Deepak Jagtap wrote: > Sure, just reported this on jira! > > Thanks & Regards, > Deepak > > On Fri, Oct 12, 2012 at 1:01 PM, Michi Mutsuzaki >wrote: > > > Hi Deepak, > > > > It's most likely a memory leak. Could you open a jira for this? > > > > Thanks! > > --Michi > > > > On Fri, Oct 12, 2012 at 12:59 PM, Deepak Jagtap > > > wrote: > > > Hi, > > > > > > I am using zookeeper-3.4.4 and frequently using multiupdate operations. > > > > > > While running valgrind it returned following output: > > > > > > ==4056== 2,240 (160 direct, 2,080 indirect) bytes in 1 blocks are > > > definitely lost in loss record 18 of 24 > > > ==4056== at 0x4A04A28: calloc (vg_replace_malloc.c:467) > > > ==4056== by 0x504D822: create_completion_entry (zookeeper.c:2322) > > > ==4056== by 0x5052833: zoo_amulti (zookeeper.c:3141) > > > ==4056== by 0x5052A8B: zoo_multi (zookeeper.c:3240) > > > > > > Just curious do I need explicitly need to handle this cleanup, by > > > invoking some API or is this a memory leak? > > > > > > It looks like completion entries for individual operations in > > > multiupdate transaction are not getting freed. The memory leak size > > > depends on the number of operations in single mutlipupdate > > > transaction. > > > > > > Thanks & Regards, > > > > > > Deepak > > > --f46d04447e73b262b904cbe6dd31--