📅 Original date posted:2015-10-14
📝 Original message: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 at 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 at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151014/57de61ea/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 17:43:18
in reply to nevent1q…sxkq
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 17:43:18Event JSON
{
"id": "47f3b5c3953789f80ab19d4d80f80658aeec5b6b501af05df7dde6e1fae9e760",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686159798,
"kind": 1,
"tags": [
[
"e",
"257c60cbd2c94bcbc1af242f96780d9665ec0aa19ec5454bed0371ff096c7c39",
"",
"root"
],
[
"e",
"fd4bb601c9552a29d8fd5e82fde634f42ff367fdc21930b33742c16c3efda861",
"",
"reply"
],
[
"p",
"dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7"
]
],
"content": "📅 Original date posted:2015-10-14\n📝 Original message:Leaks are not the only explanation possible. Caches and fragmentation can\nalso give this sort of effect. Unfortunately the tools to debug this aren't\ngreat. You could try a build with tcmalloc and use it to investigate heap\nstats.\n\nOdinn, trolling like a 3 year old will get you swiftly banned. Last warning.\nOn 14 Oct 2015 9:58 am, \"Tom Zander\" \u003ctomz at freedommail.ch\u003e wrote:\n\n\u003e On Tuesday 13 Oct 2015 14:56:08 Jonathan Toomim via bitcoin-dev wrote:\n\u003e \u003e Does anybody have any guesses where we might be leaking memory, or what\n\u003e is\n\u003e \u003e using the additional 2.4 GB? I've been using minrelaytxfee=0.00003 or\n\u003e \u003e similar on my nodes. Maybe there's a leak in the minrelaytxfee code path?\n\u003e \u003e Has anyone else seen something similar?\n\u003e\n\u003e I suggest running it in valgrind with --leak-check=full for 10 minutes.\n\u003e\n\u003e valgrind --leak-check=full src/bitcoind 2\u003e\u00261 | tee out\n\u003e\n\u003e This at least will show you any memory leaks at exit.\n\u003e Naturally, the leaks you observe may just be design issues where cache can\n\u003e grow to much and when the cache is cleaned on shutdown you won't see it in\n\u003e the\n\u003e valgrind output.\n\u003e\n\u003e --\n\u003e You received this message because you are subscribed to the Google Groups\n\u003e \"bitcoin-xt\" group.\n\u003e To unsubscribe from this group and stop receiving emails from it, send an\n\u003e email to bitcoin-xt+unsubscribe at googlegroups.com.\n\u003e For more options, visit https://groups.google.com/d/optout.\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151014/57de61ea/attachment.html\u003e",
"sig": "2c8dabd06ac9d1779f0276ea758f3754b1247caa468148f865144b69defa9d18e1cbf50eacf0df857326febca4b2158719aac65ccccbef5a9ac8814142664c27"
}