Gwibber causing beam.smp to cause high CPU load and memory usage

Bug #657478 reported by Pernig
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: gwibber

I have noticed my computer has been running a little slow for a while. I tried to get to the bottom of it and realised that 'beam.smp' was using a lot of RAM. To combat this bug, I went to System > Preferences > Broadcast Preferences and unticked the choice; 'Start service at log-in'.

Now, if I try to start Gwibber beam.smp memory usage drastically increases again, but also CPU load is very high, and after waiting five minutes the application did not load.

I have not used Gwibber beyond trying it out when I first installed Lucid, but have it installed on my machine and my Facebook account has been entered on there.

I am using Ubuntu Lucid 64-bit. If any further information is needed, please ask.

Link to a related Ubuntu Forums post. http://ubuntuforums.org/showthread.php?t=1584326

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

the bug is already fixed in maverick as we dont use desktopcouch in Ubuntu 10.10 anymore.

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

ok correcting the previous statement. gwibber in 10.10 does not use desktopcouch

Revision history for this message
Victor Vargas (kamus) wrote :

any news about this issue?

Changed in gwibber (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ferrix Hovi (ferrix) wrote :

I had this repeating on my system even with Maverick. The system is one upgraded from Lucid. Would it be possible that the gwibber is still using the wrong database? Disabling gwibber did help. Also, I think this is a recent problem that has not appeared during the time using Lucid.

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

Thanks for the bug report. This particular bug has already been reported and is a duplicate of bug 458453, so is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to report any other bugs you may find.

PS: I recommend you use gwibber 2.32.2 from gwibber-team ppa https://launchpad.net/~gwibber-team/+archive/ppa which should be quite stable

Changed in gwibber (Ubuntu):
status: Incomplete → New
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.