[gaim1.5 and 2beta]100% cpu useage when over a dozen tabs are open

Bug #45562 reported by KarlGoetz
14
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Using gaim 1.5 and 2 beta, i have a problem where the more tabs are open the more cpu useage goes up. half a dozen tabs its negligable, but at 12-18 tabs resizing the chat window or simply talking results in 100% cpu usage. This happens on 2 boxes, and is repeatable but not a crash as such.

I'm connected to ircx3, msn, icq, jabberx2,google talk.
Whats even more annoying is that after the first line of text the cpu usage drops right off untill you send that message, and then its 100% (or lots) again.

Revision history for this message
Luke Schierer (lschiere) wrote :

I cannot duplicate this with 2b3, what gtk theme are you using? does it go away if you change the theme? are you doing anything funky like playing with xorg's composite stuff?

Revision history for this message
KarlGoetz (kgoetz) wrote : Re: [Bug 45562] Re: [gaim1.5 and 2beta]100% cpu useage when over a dozen tabs are open

Luke Schierer wrote:
> I cannot duplicate this with 2b3, what gtk theme are you using? does
> it go away if you change the theme? are you doing anything funky like
> playing with xorg's composite stuff?
>

i'm using the "human" theme on both machines (ubuntu default). Its
followed me through 2 installs on one machine. I dont have anything
(like xgl/dual head) going on the computer i use for chat currently.
I switched to clearlooks (plain switch, not log in/out), and it still
happens. there was almost nothing visible cpu useage wise at 7 irc tabs,
but at 9 it was quite clear.
I'm connected to
irc.gnome.org
irc.oftc.net
irc.freenode.net
msn
jabber (.org.au)
jabber (.org)
jabber (gmail.com - google talk)
icq

The ones with active tabs are freenode and gnome.org. disabling oftc
didnt seem to make much difference.

Revision history for this message
KarlGoetz (kgoetz) wrote :

I just had a thought.
This could actualy be a GTK issue, as i have issues with Firefox when i have over a dozen tabs open, and a few misc issues around the place.
Think it could be a GTK problem, or am i way off course?
kk

KarlGoetz (kgoetz)
Changed in gaim:
status: Unconfirmed → Needs Info
Revision history for this message
Milton Pividori (miltondp) wrote :

Similar problem here. Gaim uses a lot of CPU not when I open many tabs, but when someone uses animated icons. In that conversation, when a send a message, it takes a lot of time to display the text. This does not happen when both don't use animated icons.

All this happens with Gaim 2.0.0+beta3.1-1ubuntu9 (Sorry for my English).

Revision history for this message
Milton Pividori (miltondp) wrote :

I realized that all this happens when the powernowd service is running. The freq of my CPU is reduced to 800 MHz and that's why all the gnome desktop (principally gaim, as I described above) become slower. If you disable powernowd that's resolved. However it should not happen.

Revision history for this message
Sebastien Bacher (seb128) wrote :

KarlGoetz, do you use powernowd too?

Revision history for this message
KarlGoetz (kgoetz) wrote : Re: [Bug 45562] Re: [gaim1.5 and 2beta]100% cpu useage when over a dozen tabs are open

Sebastien Bacher wrote:
> KarlGoetz, do you use powernowd too?
>
the daemon may be running, but my cpu doesn't scale.
kk

Revision history for this message
Daniel Holbach (dholbach) wrote :

Is this still a gaim problem?

Revision history for this message
Júlio Alexandrino (alexandrino) wrote :

Using Gaim 2.0.0 beta 6, (included in Feisty), I opened 30 tabs and noticed no dramatic increase in CPU usage. I was able to resize the window and shuffle through the tabs (using the left and right arrows) and everything worked as it should.

I think that this was probably fixed by now.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Marking as Fixed then. Thanks for following up.

Changed in gaim:
status: Needs Info → 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.