📅 Original date posted:2015-10-14
📝 Original message: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.
Tom Zander [ARCHIVE] /
npub1mj…dxnq7
2023-06-07 17:43:18
in reply to nevent1q…zsps
Author Public Key
npub1mju50kqcm07heu967fkq6h4kq666xgekc4yrldf7q52xx9vr8jnsrdxnq7Published at
2023-06-07 17:43:18Event JSON
{
"id": "fd4bb601c9552a29d8fd5e82fde634f42ff367fdc21930b33742c16c3efda861",
"pubkey": "dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7",
"created_at": 1686159798,
"kind": 1,
"tags": [
[
"e",
"257c60cbd2c94bcbc1af242f96780d9665ec0aa19ec5454bed0371ff096c7c39",
"",
"root"
],
[
"e",
"52d90f4fb29b76b2b7176699acff359f8beef1b0854c328731c15d80312a5e3f",
"",
"reply"
],
[
"p",
"d2fc92ecd9d7550ff504a6cac34209a57de565581b702092d5c17d367f2bcbae"
]
],
"content": "📅 Original date posted:2015-10-14\n📝 Original message:On Tuesday 13 Oct 2015 14:56:08 Jonathan Toomim via bitcoin-dev wrote:\n\u003e Does anybody have any guesses where we might be leaking memory, or what is\n\u003e using the additional 2.4 GB? I've been using minrelaytxfee=0.00003 or\n\u003e similar on my nodes. Maybe there's a leak in the minrelaytxfee code path?\n\u003e Has anyone else seen something similar?\n\nI suggest running it in valgrind with --leak-check=full for 10 minutes.\n\n valgrind --leak-check=full src/bitcoind 2\u003e\u00261 | tee out\n\nThis at least will show you any memory leaks at exit.\nNaturally, the leaks you observe may just be design issues where cache can \ngrow to much and when the cache is cleaned on shutdown you won't see it in the \nvalgrind output.",
"sig": "72336d6aa11acc8682e1122ca0675346f0c10364b6d7f6abef38ddade0497c95aaf0dc68a33423b7bd7f5e397117b4e831c98427e1a5cedb73a346f24fb45e65"
}