MIME-Version: 1.0
In-Reply-To: <2354813.5q0TUrZsWe@garp>
References: <99C42DE7-814A-48F8-AB28-A5ADD77A9FD9@toom.im>
	<2354813.5q0TUrZsWe@garp>
Date: Wed, 14 Oct 2015 11:09:40 +0200
Message-ID: <CA+w+GKTYNxmCR_mcTmu=u8RkjkJqOD=6_SKsfygGjXB-YpWBXQ@mail.gmail.com>
From: Mike Hearn <hearn@vinumeris.com>
To: bitcoin-xt <bitcoin-xt@googlegroups.com>
Content-Type: multipart/alternative; boundary=001a1141fb902e200405220cece2
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Memory leaks?
Precedence: list

--001a1141fb902e200405220cece2
Content-Type: text/plain; charset=UTF-8

Leaks are not the only explanation possible. Caches and fragmentation can
also give this sort of effect. Unfortunately the tools to debug this aren't
great. You could try a build with tcmalloc and use it to investigate heap
stats.

Odinn, trolling like a 3 year old will get you swiftly banned. Last warning.
On 14 Oct 2015 9:58 am, "Tom Zander" <tomz@freedommail.ch> wrote:

> 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.
>
> --
> You received this message because you are subscribed to the Google Groups
> "bitcoin-xt" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoin-xt+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

--001a1141fb902e200405220cece2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Leaks are not the only explanation possible. Caches and frag=
mentation can also give this sort of effect. Unfortunately the tools to deb=
ug this aren&#39;t great. You could try a build with tcmalloc and use it to=
 investigate heap stats.</p>
<p dir=3D"ltr">Odinn, trolling like a 3 year old will get you swiftly banne=
d. Last warning.</p>
<div class=3D"gmail_quote">On 14 Oct 2015 9:58 am, &quot;Tom Zander&quot; &=
lt;<a href=3D"mailto:tomz@freedommail.ch">tomz@freedommail.ch</a>&gt; wrote=
:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tuesday 13 Oct =
2015 14:56:08 Jonathan Toomim=C2=A0 via bitcoin-dev wrote:<br>
&gt; Does anybody have any guesses where we might be leaking memory, or wha=
t is<br>
&gt; using the additional 2.4 GB? I&#39;ve been using minrelaytxfee=3D0.000=
03 or<br>
&gt; similar on my nodes. Maybe there&#39;s a leak in the minrelaytxfee cod=
e path?<br>
&gt; Has anyone else seen something similar?<br>
<br>
I suggest running it in valgrind with --leak-check=3Dfull for 10 minutes.<b=
r>
<br>
=C2=A0 valgrind --leak-check=3Dfull src/bitcoind 2&gt;&amp;1 | tee out<br>
<br>
This at least will show you any memory leaks at exit.<br>
Naturally, the leaks you observe may just be design issues where cache can<=
br>
grow to much and when the cache is cleaned on shutdown you won&#39;t see it=
 in the<br>
valgrind output.<br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;bitcoin-xt&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoin-xt%2Bunsubscribe@googlegroups.com">bitcoi=
n-xt+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href=3D"https://groups.google.com/d/optout" rel=
=3D"noreferrer" target=3D"_blank">https://groups.google.com/d/optout</a>.<b=
r>
</blockquote></div>

--001a1141fb902e200405220cece2--