gwibber-daemon takes too much cpu
Bug #451360 reported by
markuz
This bug report is a duplicate of:
Bug #554005: Using some glib functions within multiprocessing from a threaded app sometimes causes 100% CPU utilization.
Edit
Remove
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Confirmed
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Using gwibber 2.0.0 (from gwibber ppa).
Gwibber was using a fairly small amount of my cpu time, but since a week ago it takes a lot, fortunately I have a 2 cores cpu and didn't feel that my system get slow, but a single process using one core 90% of the time is a sign that something is wrong.
May there be a while cycle that is causing this?. maybe an gobject's idle_add ?. By the time I don't know what triggers the daemon to use that amount of cpu time, but whatever it is it shouln't be.
Anything I can do for you just tell me :-)
The workaround I have been doing is using cpulimit to restrict the amount of CPU that gwibber-daemon can use.
Changed in gwibber: | |
status: | New → Confirmed |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Medium |
Changed in gwibber (Ubuntu): | |
status: | New → Triaged |
To post a comment you must log in.
Could you try disabling Facebook in Gwibber and then restarting the daemon? Does this problem still show up when you have Facebook disabled?