Recently, znc started using about 20% CPU (as seen from htop) when doing nothing.
Here's the loop znc is stuck into as seen by strace (shortened a bit for readability);
It looks like poll timeouts after 1ms and tries to send again the same block of data on the same file descriptor. Which is still not ready. The whole ordeal repeats every few ms.
For what it's worth, the CPU is an AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55.
My znc config has 29 users and 31 networks.
The modules loaded on at least some of the configured networks: autocycle bouncedcc buffextras chansaver clearbufferonmsg controlpanel corecaps identfile kickrejoin lastseen nickserv perform sasl savebuff stickychan
The output of lsof -np 38200 for the file descriptor znc tries to write to in this loop.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi,
Recently, znc started using about 20% CPU (as seen from htop) when doing nothing.
Here's the loop znc is stuck into as seen by strace (shortened a bit for readability);
It looks like poll timeouts after 1ms and tries to send again the same block of data on the same file descriptor. Which is still not ready. The whole ordeal repeats every few ms.
For what it's worth, the CPU is an
AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55.My znc config has 29 users and 31 networks.
The modules loaded on at least some of the configured networks: autocycle bouncedcc buffextras chansaver clearbufferonmsg controlpanel corecaps identfile kickrejoin lastseen nickserv perform sasl savebuff stickychan
The output of
lsof -np 38200for the file descriptor znc tries to write to in this loop.The network it's trying to connect to is long dead. The address is
irc.epd-me.net +6660.I'm on Debian trixie and my znc version is:
Hope this helps.