Join Nostr
2026-08-10 14:17:55 UTC
in reply to

Dave on Nostr: The leak is in the latest v0.12.0 code? It should monitor it's own memory and do a ...

The leak is in the latest v0.12.0 code? It should monitor it's own memory and do a reset if it detects memory usage has grown too high. Historically, QUIC connections have eaten up a lot of memory per connection, so this recycle code had to exist.

Also, are you building the binary with debug or --release? Building with --release makes a huge impact on reducing memory consumption.