From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2C9509D for ; Wed, 14 Oct 2015 07:58:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx-out02.mykolab.com (mx01.mykolab.com [95.128.36.1]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 38F7ACC for ; Wed, 14 Oct 2015 07:58:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) by mx-out02.mykolab.com (Postfix) with ESMTPS id 25BDA621F9; Wed, 14 Oct 2015 09:58:50 +0200 (CEST) From: Tom Zander To: bitcoin-dev@lists.linuxfoundation.org, bitcoin-xt@googlegroups.com Date: Wed, 14 Oct 2015 08:58:48 +0100 Message-ID: <2354813.5q0TUrZsWe@garp> In-Reply-To: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im> References: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im> Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Memory leaks? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 07:58:54 -0000 On Tuesday 13 Oct 2015 14:56:08 Jonathan Toomim via bitcoin-dev wrote: > Does anybody have any guesses where we might be leaking memory, or what is > using the additional 2.4 GB? I've been using minrelaytxfee=0.00003 or > similar on my nodes. Maybe there's a leak in the minrelaytxfee code path? > Has anyone else seen something similar? I suggest running it in valgrind with --leak-check=full for 10 minutes. valgrind --leak-check=full src/bitcoind 2>&1 | tee out This at least will show you any memory leaks at exit. Naturally, the leaks you observe may just be design issues where cache can grow to much and when the cache is cleaned on shutdown you won't see it in the valgrind output.