Transaction

ba8f1df37970f951c92f19aa6be81850211fdb00a8fcfe0b2b5f7e32ba76b89d
Timestamp (utc)
2024-03-23 20:07:44
Fee Paid
0.00000013 BSV
(
0.02457277 BSV
-
0.02457264 BSV
)
Fee Rate
10.18 sat/KB
Version
1
Confirmations
99,559
Size Stats
1,277 B

2 Outputs

Total Output:
0.02457264 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Hmm, now the bug is gone though I remember how it was. That's the compiled release binary, 0.3.12 as I already mentioned. I didn't use -connect. Flickering was fast from 0 to 2 (less than half second) and then there was a pause in about a second with 0 connections. So the flicker itself was almost every second (not faster). Looks like it got connrefused instantly or such. I watched logs, sorry didn't saved them but there was nothing interesting just connect and disconnect without a reason.<br/><br/>I measured the RES memory with htop. It updates once per second that's why I can't see the real leak speed. Now the client tries to connect after startup and flickers 0-2, too, but just 5-10 times and then establishes one connection. Then it flickers between 1 and 3 and no leaks happen. Then connection number grows up to 40 or even more, everything is stable. To reproduce this try to switch off the network connection right after the client gets IPs from IRC so it will try to connect and fail.</div> text/html
    https://whatsonchain.com/tx/ba8f1df37970f951c92f19aa6be81850211fdb00a8fcfe0b2b5f7e32ba76b89d