Re: Memory leak
You're connecting to yourself. All 21 connection attempts were to a node with version 31300 (0.3.13). Not everyone has 0.3.13 yet.
IRC seems to be working. It ought to have other nodes to try.
There may be something I need to do to make sure it doesn't try to connect to itself again right away after disconnecting. I can't see how it's happening though, it should be resetting nLastTry which would put it to the back of the queue, but the log doesn't show it.
You can try moving addr.dat aside. Maybe there's something wrong in it.
Are you using -addnode?
Fonte: https://satoshi.nakamotoinstitute.org/posts/bitcointalk/481/
Satoshi Posts
npub1km…l6khs
2025-04-21 08:18:09
Author Public Key
npub1km3kxykvt4u4d8twn2mhhdfyd6z8e5kmkdtjc8rxqm0em0tunzjscl6khsPublished at
2025-04-21 08:18:09Event JSON
{
"id": "99afd4796f80f7f3ebd8c70a2450114e01dcbd8a0a4970242edfe839fac1a232",
"pubkey": "b6e36312cc5d79569d6e9ab77bb5246e847cd2dbb3572c1c6606df9dbd7c98a5",
"created_at": 1745223489,
"kind": 1,
"tags": [],
"content": "Re: Memory leak\n\nYou're connecting to yourself. All 21 connection attempts were to a node with version 31300 (0.3.13). Not everyone has 0.3.13 yet.\nIRC seems to be working. It ought to have other nodes to try.\nThere may be something I need to do to make sure it doesn't try to connect to itself again right away after disconnecting. I can't see how it's happening though, it should be resetting nLastTry which would put it to the back of the queue, but the log doesn't show it.\nYou can try moving addr.dat aside. Maybe there's something wrong in it.\nAre you using -addnode?\n\nFonte: https://satoshi.nakamotoinstitute.org/posts/bitcointalk/481/",
"sig": "6808a04dcb7afc9d0496fd1728a3b21a8aaf1e2f41311a831ba8ac0748e074b52b3a3f11f8d8b7b13a4f971dd2be4da1f3cb2fae13af4c7e33ada01ef047cf9c"
}