When using Halloy connected to ZNC with the Clientbuffer module memory usage grows continually during use. When otherwise running Halloy I see memory usage start around 100MB and grow up to around 150MB, but when connected to ZNC with the Clientbuffer module memory grows unbounded. In around an hour memory is often up to 250MB and the UI slows down, but memory use will continue to grow until the application stalls and must be force quit. The largest memory use I've seen so far is 3.5GB, but usually I don't let it get that high.
It doesn't matter whether I use the new nickname format or not (i.e. using an @ in my username to identify the client is not necessary to produce the behavior). It seems to progress faster when two clients are connected to the ZNC bouncer, but it still happens when only one client is connected. Happens on Linux (both x86_64 and aarch64, though it progresses faster on the latter). I tried reproducing it under DHAT (valgrind), but annoying it does not seem to reproduce no matter how long I wait.
One thing I have noticed, is that the server buffer gets a lot of RPL_WHOREPLY messages in it. I think this is somewhat expected when two (or more) clients are connected, since last_who will not (to my knowledge) reflect the WHO requests from another client (i.e. all the WHO polls sent from another client will show up in the server buffer). For some reason this also happens when only one client is connected. Since the server buffer history is capped at 10000 messages (as far as I know) I don't expect it to causing the memory leak, but it's the only different behavior I've been able to spot so far.
When using Halloy connected to ZNC with the Clientbuffer module memory usage grows continually during use. When otherwise running Halloy I see memory usage start around 100MB and grow up to around 150MB, but when connected to ZNC with the Clientbuffer module memory grows unbounded. In around an hour memory is often up to 250MB and the UI slows down, but memory use will continue to grow until the application stalls and must be force quit. The largest memory use I've seen so far is 3.5GB, but usually I don't let it get that high.
It doesn't matter whether I use the new nickname format or not (i.e. using an
@in my username to identify the client is not necessary to produce the behavior). It seems to progress faster when two clients are connected to the ZNC bouncer, but it still happens when only one client is connected. Happens on Linux (both x86_64 and aarch64, though it progresses faster on the latter). I tried reproducing it under DHAT (valgrind), but annoying it does not seem to reproduce no matter how long I wait.One thing I have noticed, is that the server buffer gets a lot of
RPL_WHOREPLYmessages in it. I think this is somewhat expected when two (or more) clients are connected, sincelast_whowill not (to my knowledge) reflect theWHOrequests from another client (i.e. all theWHOpolls sent from another client will show up in the server buffer). For some reason this also happens when only one client is connected. Since the server buffer history is capped at 10000 messages (as far as I know) I don't expect it to causing the memory leak, but it's the only different behavior I've been able to spot so far.