gwibber-service consumes 100% CPU when the network is down

[Jamu Kakar]

I have the following packages installed:

ii gwibber 2.91.1-0maverick1 Open source social networking client for GNOME
ii gwibber-service 2.91.1-0maverick1 Open source social networking client for GNOME
ii gwibber-service-facebook 2.91.1-0maverick1 Facebook plugin for Gwibber
ii gwibber-service-statusnet 2.91.1-0maverick1 Status.Net plugin for Gwibber
ii gwibber-service-twitter 2.91.1-0maverick1 Twitter plugin for Gwibber
ii libgwibber0 0.0.6-0ubuntu1 Gwibber - shared library

Last week I was on a network with heavy packet loss (something like
40-80%)... occassionally the connection would just die (100% packet
loss, but still "connected") and gwibber-service (two instances of
them) would each consume 100% CPU (thus DoSing both cores on my
machine). It would fix itself if the network connection was restored.

[malclocke (malc-wholemeal)]

Ditto here, default packages on Maverick show same behaviour.

[Bilal Shahid (s9iper1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better,
* can you reproduce it ?
* if so than which version are you on ?

[Jamu Kakar (jkakar)]

I tried to reproduce this today but with no luck. So either:

1. The issue is fixed. I think this is the case, because I haven't
   observed this issue for a long time and I've been using a lot of
   different/laggy networks for the last six months.

2. My testing method wasn't good. I tried two things: I disconnected
   the network and watched Gwibber in htop for awhile. I also used
   'tc' to make my interface randomly drop packets. In both cases,
   Gwibber performed well.

So I think this should probably be marked 'Invalid'. I'll do that now
and if I'm wrong about it this bug can be reopened.