gwibber-daemon takes too much cpu

Bug #451360 reported by markuz
56
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.

Revision history for this message
Ryan Paul (segphault) wrote :

Could you try disabling Facebook in Gwibber and then restarting the daemon? Does this problem still show up when you have Facebook disabled?

Revision history for this message
markuz (markuz) wrote :

I'm doing it right now and I will check today for gwibber-daemon cpu usage and report it on the noon.

Revision history for this message
Martin Ling (martin-launchpad) wrote :

I'm having a similar problem with 2.0.0~bzr466-0ubuntu1 which is now in the karmic repository.

I dealt with this a few times by just killing the gwibber-daemon process.

Then just now, this was happening with just a gwibber-daemon, and no gwibber process, running. I then launched gwibber from the indicator applet, and when I switched from 'Home' to 'Messages', gwibber-daemon stopped using the CPU.

Revision history for this message
Martin Ling (martin-launchpad) wrote :

It went back to using full CPU a few minutes later. Opening and poking at gwibber didn't have any effect this time. But it's now gone back to using no CPU again without further intervention.

I tried attaching strace to it, but just got:

restart_syscall(<... resuming interrupted call ...>

Revision history for this message
markuz (markuz) wrote :

I disabled my facebook account form gwibber and it isn't using a lot my cpu, is more reasonable now.

Revision history for this message
markuz (markuz) wrote :

Just to confirm. disabling facebook account gwibber-daemon stops using all my cpu.

Foppe Hemminga (foppe)
Changed in gwibber:
status: New → Confirmed
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Kai Mast (kai-mast) wrote :

I am using facebook too and gwibber nearly brings my system to freeze...

Omer Akram (om26er)
Changed in gwibber (Ubuntu):
status: New → Triaged
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Am using the version of Gwibber packaged in Ubuntu Lucid, and am experiencing very heavy CPU usage, which appears to happen when it looks for updates from the various services I have accounts registered with it for (which includes Facebook).

Revision history for this message
Omer Akram (om26er) wrote :

This bug is about gwibber-daemon and I now gwibber dont have gwibber daemon. the new service is gwibber-services so should this bug be closed?

Revision history for this message
Omer Akram (om26er) wrote :

I am marking this fixed as I wrote in the last comment now in the development release (2.29.xx) there is no service with the name gwibber-daemon and the new service is 'gwibber-services' which dont seem to be using much of my ram.

Changed in gwibber (Ubuntu):
status: Triaged → Fix Released
Changed in gwibber:
status: Confirmed → Fix Released
Revision history for this message
WalterCool (waltercool) wrote :

2.29.92.1 is eating my CPU

Using Fb, twitter and identi.ca

Without fb, still eating a lot of CPU

Revision history for this message
Julian Lam (julian-lam) wrote :

I wouldn't consider it fixed. It may be renamed gwibber-services, but it's still hogging my CPU!

Changed in gwibber:
status: Fix Released → Confirmed
Changed in gwibber (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Julian Lam (julian-lam) wrote :

(Also, I believe that "Fix Released" means an actual problem was fixed and released. Problems that resolve themselves without further intervention are usually marked Invalid. Correct me if I am wrong.)

Revision history for this message
Seth Hikari (sethhikari) wrote :

Still problem in the daily build, Takes one core to 100% but jumps around on what core.

Revision history for this message
Omer Akram (om26er) wrote :

This is an already know bug in Lucid marking this duplicate

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.