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 98BE190 for ; Wed, 14 Oct 2015 09:39:16 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EB004A1 for ; Wed, 14 Oct 2015 09:39:15 +0000 (UTC) Received: by wijq8 with SMTP id q8so72478339wij.0 for ; Wed, 14 Oct 2015 02:39:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=soWAmmkJsi2wws0hSfx+ukQenGqWFYfNp6++mCqtVoA=; b=dq3tRSINMjXE1jC5WOgv4zwKC/1pTzS8K56WfEPe3jp+4DjQHnKkd2wzKQQkFgr1ij eqzpvcRMPTVAL/imlD+G8sHuCyJBl0lwSsHVDPbQf5zn7L44/VUyxxQwvbFLb+yLpz7z C0R5Sw1qqL1JcJN9gG8REStiExkixEdyHNHO9qCKTXo1njy5YfunmPBktraWS9BTHfsx Ijww2WQWb7F238pc9p5eW5OmaaP+3lZb9u7KJEZoBLphPFYW3AZ55PeyNmpZGcU2jJKm sCfyJFjf5wibm7PeNI528KdZVzHV9Xfqb3996+Xh2MGJAvDafaEAQoFdm5w9H8eXV4HJ QBrg== X-Received: by 10.195.12.164 with SMTP id er4mr2747520wjd.9.1444815554535; Wed, 14 Oct 2015 02:39:14 -0700 (PDT) Received: from amethyst.visucore.com (dhcp-089-098-228-253.chello.nl. [89.98.228.253]) by smtp.gmail.com with ESMTPSA id lb10sm8875032wjc.9.2015.10.14.02.39.13 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 14 Oct 2015 02:39:14 -0700 (PDT) Date: Wed, 14 Oct 2015 11:39:14 +0200 From: "Wladimir J. van der Laan" To: "Jonathan Toomim (Toomim Bros)" Message-ID: <20151014093913.GB19607@amethyst.visucore.com> References: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im> X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org, bitcoin-xt@googlegroups.com 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 09:39:16 -0000 On Tue, Oct 13, 2015 at 02:56:08PM -0700, Jonathan Toomim (Toomim Bros) via bitcoin-dev wrote: > I just noticed that several of my running bitcoind processes were using around 3+ GB of RAM, even though the mempool itself seemed to be under control. > > XXXX@prime:~/bin$ ./bitcoin-cli getmempoolinfo > { > "size" : 1896, > "bytes" : 37341328 > } > > [total memory usage not shown -- I restarted bitcoind as soon as I noticed, and didn't copy it down from top] This is *most likely* the mempool, but is just not reported correctly. In the meantime you can mitigate the mempool growth by setting `-mintxfee`, see https://github.com/bitcoin/bitcoin/blob/v0.11.0/doc/release-notes.md#transaction-flooding This will be the default in 0.11.1 and 0.10.3. 0.12.0 will have better mempool management, as well as more precise reporting (as paveljanik already mentions.) Wladimir