thanks for your answer. Sorry that I did not reply earlier... The
scenario you describe sound familiar. I was not able to figure out
exactly when the problem occurs. But yes, I am connected to an IRC
server. And once in a while, Jitsi has problems to (re)connect. I also
usually just hibernate my system.
So there is a bug in Jitsi? Is there anything I can do about it right
now? Can I help to track down the bug (if there is any) to get it fixed?
I know of a case, which I have not reproduced yet, that happens after
the system is resumed from standby. Apparently, if you have an IRC
account connected to an IRC server when the system goes into standby,
then when you get out of it, there is a chance the connection does not
restore correctly and results in 100% CPU while trying to communicate.
Is this a scenario you can relate to?
On 26-06-15 18:18, Matthias J. Sax wrote:
I am using Jitsi 2.8.5426 (on Debian Jessy) and observe that Jitsi put a
high load on the CPU (up to 100% of a single core) even if it runs in
the background (ie, no call or video is running).
The load stay high, even if I deactivate all my account and go offline.
It is a Jitsi problem or can I do something to get Jitsi "behaving nice".
Thanks for your help.