[jitsi-users] Jisti in background -- high CPU usage


#1

Hi Danny,

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?

-Matthias

···

Hi Matthias,

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?

Danny

On 26-06-15 18:18, Matthias J. Sax wrote:

Hi,

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.

-Matthias


#2

Hi Matthias,

Hi Danny,

thanks for your answer. Sorry that I did not reply earlier...

I just sent the message :wink:

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.

In that case, we might be talking about the same issue. At least, it
sounds like it.

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?

It would help if you can give me a (fairly) reliable reproduction
recipe. I'm on Ubuntu or Debian, depending on the system I'm using, but
I haven't been able to reproduce it. I hardly ever suspend/hibernate my
system, so that may explain. Just fiddling with network connectivity
doesn't seem to reproduce it.

So if you can describe the (concise) steps you use to cause this issue,
then I expect that I should be able to reproduce it too. Given that we
would be running very similar operating systems.

Danny

···

On 24-09-15 17:12, Matthias J. Sax wrote:

-Matthias

Hi Matthias,

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?

Danny

On 26-06-15 18:18, Matthias J. Sax wrote:

Hi,

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.

-Matthias

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Hi Matthias,

Hi Danny,

thanks for your answer. Sorry that I did not reply earlier...

I just sent the message :wink:

... or maybe it was a few months ago ... interesting how one can get
confused sometimes :stuck_out_tongue:

Danny

···

On 24-09-15 20:46, Danny van Heumen wrote:

On 24-09-15 17:12, Matthias J. Sax wrote:

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.

In that case, we might be talking about the same issue. At least, it
sounds like it.

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?

It would help if you can give me a (fairly) reliable reproduction
recipe. I'm on Ubuntu or Debian, depending on the system I'm using, but
I haven't been able to reproduce it. I hardly ever suspend/hibernate my
system, so that may explain. Just fiddling with network connectivity
doesn't seem to reproduce it.

So if you can describe the (concise) steps you use to cause this issue,
then I expect that I should be able to reproduce it too. Given that we
would be running very similar operating systems.

Danny

-Matthias

Hi Matthias,

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?

Danny

On 26-06-15 18:18, Matthias J. Sax wrote:

Hi,

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.

-Matthias

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

Hi Danny,

thanks for your support. It all relates to the same stuff. A few month
back, when I sent the first mail, I overlooked your reply (for whatever
reason) and thought nobody answered. Per accident I discovered your
answers now...

I am still not sure what the exact pattern is, but yes, I do hibernate
and I am in an IRC. Up to now, I was not aware that hibernating might be
related. As I now know what to look for, I try to reproduce the problem
in detail an come back to you.

-Matthias

···

On 09/24/2015 08:48 PM, Danny van Heumen wrote:

On 24-09-15 20:46, Danny van Heumen wrote:

Hi Matthias,

On 24-09-15 17:12, Matthias J. Sax wrote:

Hi Danny,

thanks for your answer. Sorry that I did not reply earlier...

I just sent the message :wink:

... or maybe it was a few months ago ... interesting how one can get
confused sometimes :stuck_out_tongue:

Danny

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.

In that case, we might be talking about the same issue. At least, it
sounds like it.

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?

It would help if you can give me a (fairly) reliable reproduction
recipe. I'm on Ubuntu or Debian, depending on the system I'm using, but
I haven't been able to reproduce it. I hardly ever suspend/hibernate my
system, so that may explain. Just fiddling with network connectivity
doesn't seem to reproduce it.

So if you can describe the (concise) steps you use to cause this issue,
then I expect that I should be able to reproduce it too. Given that we
would be running very similar operating systems.

Danny

-Matthias

Hi Matthias,

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?

Danny

On 26-06-15 18:18, Matthias J. Sax wrote:

Hi,

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.

-Matthias

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

Hi Matthias,

Hi Danny,

thanks for your support. It all relates to the same stuff. A few month
back, when I sent the first mail, I overlooked your reply (for whatever
reason) and thought nobody answered. Per accident I discovered your
answers now...

I am still not sure what the exact pattern is, but yes, I do hibernate
and I am in an IRC. Up to now, I was not aware that hibernating might be
related. As I now know what to look for, I try to reproduce the problem
in detail an come back to you.

From what I could tell from the screenshot damencho sent me a while
back, the issue is caused inside the irc-api client library that I use
for IRC connectivity. IIUC then the connection just keeps returning
0-values instead of blocking until the next batch of sensible data arrives.

There might be a standard situation for this, but I haven't found it yet.

Please do! If I can reproduce this, then it will be easier to track down
which situations cause this. Also, I don't think hibernate is *directly*
related, but I think/suspect some kind of loss of connection might be,
and by hibernating network connections are interrupted.

Danny

···

On 25-09-15 10:32, Matthias J. Sax wrote:

-Matthias

On 09/24/2015 08:48 PM, Danny van Heumen wrote:

On 24-09-15 20:46, Danny van Heumen wrote:

Hi Matthias,

On 24-09-15 17:12, Matthias J. Sax wrote:

Hi Danny,

thanks for your answer. Sorry that I did not reply earlier...

I just sent the message :wink:

... or maybe it was a few months ago ... interesting how one can get
confused sometimes :stuck_out_tongue:

Danny

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.

In that case, we might be talking about the same issue. At least, it
sounds like it.

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?

It would help if you can give me a (fairly) reliable reproduction
recipe. I'm on Ubuntu or Debian, depending on the system I'm using, but
I haven't been able to reproduce it. I hardly ever suspend/hibernate my
system, so that may explain. Just fiddling with network connectivity
doesn't seem to reproduce it.

So if you can describe the (concise) steps you use to cause this issue,
then I expect that I should be able to reproduce it too. Given that we
would be running very similar operating systems.

Danny

-Matthias

Hi Matthias,

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?

Danny

On 26-06-15 18:18, Matthias J. Sax wrote:

Hi,

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.

-Matthias

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users