Pidgin taking 100+% CPU at random times

Bug #480946 reported by Daniel McAloon
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Installed: 1:2.6.2-1ubuntu7

Support thread on the forums:
http://ubuntuforums.org/showthread.php?t=1314358

Problem summary: After roughly 18 hours of running pidgin, CPU use goes to 100+%. A single pidgin process can be using up to 190% CPU on a dual-core machine. Problem seems to be temporarily fixed by reboots.

Long version:
A few days after upgrading to 9.10 from 9.04, pidgin began using 100+% CPU. Re-installing libpurple and rebooting seemed to fix it, but then the problem returned. Re-installing ATI drivers seemed to fix it, but then the problem returned. After 18 hours of running (I leave the machine on at night) pidgin will begin taking 100+% CPU. It continues responding at this time, and I can use it (rather smoothly, actually), but everything else is fighting for CPU time. Killing pidgin obviously fixes this issue. I can safely reload pidgin and browse my buddies without introducing the CPU load. I can open new chat window without incident. Sending the first message to the other person will immediately peg the CPU. This is only the case if the machine has not been rebooted recently (apparently).

You should have crash reports attached to this bug, but launchpad was down when it first attempted to load, so if not let me know and I'll re-gen.

ProblemType: Bug
Architecture: i386
Date: Wed Nov 11 15:21:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: fglrx
Package: pidgin 1:2.6.2-1ubuntu7
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: pidgin
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Daniel McAloon (maniacdan) wrote :
Revision history for this message
Daniel McAloon (maniacdan) wrote :

Plugins don't effect the issue either, it manifests with all plugins off.

Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Which protocol do you use when sending the first message to your buddy?

This will help us to find and resolve the problem.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel McAloon (maniacdan) wrote : Re: [Bug 480946] Re: Pidgin taking 100+% CPU at random times

I don't actually have the machine anymore that was causing this issue (it
was a work box and I've switched jobs). After the upgrade to 10 beta the
issue resolved itself, I forgot to close the issue.

There is a new, unrelated bug that I'm going to file, but I won't reuse this
ticket for that.

Thanks,
Daniel

On Jul 16, 2010 5:15 AM, "Robert Roth" <email address hidden> wrote:

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Which protocol do you use when sending the first message to your buddy?

This will help us to find and resolve the problem.

** Changed in: pidgin (Ubuntu)
      Status: New => Incomplete

--
Pidgin taking 100+% CPU at random times
https://bugs.launchpad.net/bugs/480946
You received thi...
Status in “pidgin” package in Ubuntu: Incomplete

Bug description:
Binary package hint: pidgin

Installed: 1:2.6.2-1ubuntu7

Support thread on the fo...
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/480946/+subscribe

Robert Roth (evfool)
Changed in pidgin (Ubuntu):
status: Incomplete → Fix Released
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.