100% CPU usage

[Facundo Batista]

Binary package hint: gwibber

Just after boot, I wait a couple a of minutes and see that the whole time gwibber-service was busy using 100% of one of my CPUs. I need to kill it to get it out from that state.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic-pae 2.6.35.4
Uname: Linux 2.6.35-20-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Sep 8 09:41:14 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=es_AR.utf8
 SHELL=/bin/bash
SourcePackage: gwibber

[Victor Vargas (kamus)]

I haven't seen this issue since lots of releases ago, please could you upgrade your current version to the latest included in Maverick and check if is still occurring? Thanks.

[Facundo Batista (facundo)]

I experienced this again this morning.

Note that I may found something that could indicate what could be happening: I suffered from some issues in my internet connection. It went flaky, disappeared, back on again, down, flaky, and finally up and ok.

While suffering these networking issues, there were three gwibber-services consuming lot of CPU (*lot*, like almost 100% each).

[Victor Vargas (kamus)]

Facundo, have you checked if this behaviour is still reproducible with latest release of gwibber 2.32.0.1-0ubuntu1?

[Facundo Batista (facundo)]

Still happens, :(

I reproduced today, also with an ugly network: NetworkManager was connected, but there wasn't really internet (only LAN).

Screenshot attached.

[Victor Vargas (kamus)]

Last night I was facing connectivity issues here and can reproduce it too, gwibber-service consumes almost 100% of my CPU and then a second instance is doing same thing.

[Gert van Dijk (gertvdijk)]

Also affected by this bug. Particularly irritating when resume from suspend, which I do a few times a day generally. Most of the times the network is unreachable for a number of seconds, so I guess that's the cause for it.

[Ken VanDine (ken-vandine)]

All those affected by this bug, can you comment with what your refresh interval is set to? And if it is under 10 minutes please bump it up to 10 minutes and see if it happens again.

I suspect when there are network related issues, which prevent a full refresh from completing before the next scheduled interval, it blocks. However, those threads doing the work should time out after 240s, but we have seen bugs in the past where the timeout wasn't killing the thread.

[Gert van Dijk (gertvdijk)]

For me the refresh interval is set to 15 minutes, the default - I didn't touch it.

[Jamu Kakar (jkakar)]

I wonder if bug 682779 is related... I filed it today and am seeing
100% CPU usage, in spurts, even with a good network connection.

[Martin Schröder (martinschroeder)]

I don't think, that #306497 is a duplicate, there the problem is memory consumption.

Here, the problem is high cpu usage (for me 100% on one core). I really think, the problem has to do with a bad network connection.

Note, that the error occurs, even if i don't have gwibber installed, only gwibber-service is running (and i can't remove the package, because that would also remove the indicator-me package, which would be very annoying).