Bug 216289 - kopete makes plasma use much CPU power
Summary: kopete makes plasma use much CPU power
Status: RESOLVED DUPLICATE of bug 314919
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 1.0.80
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
: 265252 (view as bug list)
Depends on:
Reported: 2009-11-26 18:54 UTC by dcent
Modified: 2013-07-02 22:08 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:

sysprof (7.33 KB, application/x-7z-compressed)
2011-01-15 02:14 UTC, Paulo Neves

Note You need to log in before you can comment on or make changes to this bug.
Description dcent 2009-11-26 18:54:07 UTC
Version:           4.3.1 (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

After running Kopete for ~60 minutes, the CPU usage goes up to 30%, showing "Xorg" causes that. Restarting plasma/KDE resets the situation. I think it's happening because of the animation in kicker when I receive a new message, because if I let the kopete icon 'dance' for > 15 minutes, the animation is kind of "stuck" and the CPU load goes up.
Comment 1 Dario Andres 2009-11-26 22:43:47 UTC
- Do you use the Lancelot menu ?
Comment 2 dcent 2009-11-27 14:19:10 UTC
Never heard of that, so I guess I don't.
Comment 3 Marcelo Sales 2010-10-16 17:02:51 UTC
I can confirm this and I think it is indeed related to the kopete notification for new messages.
When a new message arrives, the kopete animated notification icon is displayed in the notification area of the plasma panel. If you click it or open kopete to see the message that arrived within a few minutes, nothing abnormal happens.
However, if you let the animated icon unattended for some time, it occasionally will become static and the plasma panel almost freezes. Other applications continue running normally. When the plasma panel is in this state, anything you click on it does not respond immediately, but will respond eventually, some times after a reasonably long time.
If you then click the kopete notification icon, eventually the kopete window will open to show the new message and the icon disappears from the notification area. After that, the plasma panel will gradually return to normality and will become responsive again after a few minutes (normally 5-7 minutes).
This happens everytime some one sends me a message while my computer is unattended. When I come back, the plasma panel is unresponsive.
As far as I can see, this has nothing to do with for how long kopete is running, but with for how long you ignore its notifications when a new message arrives.
Comment 4 Marcelo Sales 2010-10-16 17:13:20 UTC
Just adding, a use a vertical plasma panel, don't know if it makes any difference. And I do not use Lancelot either.
Comment 5 Paulo Neves 2011-01-15 02:14:35 UTC
Created attachment 56033 [details]
Comment 6 Paulo Neves 2011-01-15 02:15:07 UTC
I can also confirm this. More time the kopete notification icon spins on system tray, more cpu it will use, even after I stop kopete, high CPU usage will go for some 10 or 20 minutes. 
After doing a quick profile with sysprof, I found that something was wrong with GetXIDRange (xserver) as it had the highest usage.
Comment 7 Frank Niethardt 2011-01-31 22:03:18 UTC
Same problem here. The spinning Kopete icon makes plasma-desktop use a full core of my CPU. This problem was "fixed" in between by stopping the sping after a couple of seconds. I guess the plasma rewrite reenabled the problem.

Qt: 4.7.1
KDE Development Platform: 4.6.00 (4.6.0)
Plasma Desktop Shell: 0.4

Archlinux packages
Comment 8 Samuel Brack 2011-03-13 15:33:43 UTC
The problem still exists with Kopete 1.0.80 on KDE 4.6.1 on Archlinux. Are there any news on this?
Comment 9 Lamarque V. Souza 2011-05-16 21:54:36 UTC
*** Bug 265252 has been marked as a duplicate of this bug. ***
Comment 10 zbynek.jun 2011-05-16 22:07:51 UTC
Same problems on Gentoo with kde 4.6.3, kernel, X.Org 1.9.5 Qt 4.7.2 and stock intel graphics kernel driver.
Comment 11 hl-kde 2011-08-05 07:12:36 UTC
same problem here with openSUSE 11.4 / kde 4.6.0 in enterprise environment. (desktop effects switched off, mostly (closedsource) nvidia graphics driver)

After some hours of spinning kopete icon, plasma desktop switching gets painfull slow (several seconds for the simple switch). The whole Xorg "feels" slower. 

I can observe the bug in "xrestop". After start, the process plasma-desktop needs about 15M x11-pixmap memory in <500 Pixmaps (colums "Pxm mem" and "Pxms"). 

While the kopete icon is animated, Pxms grows about 10 per second. If a user is away for a while, I observed a memory consumption of ~80M (instead of 15M) for plasma desktop. 

My current workaround: restart plasma (~10secs) to speed up Xorg again and/or switch off kopete icon animation. 

  killall plasma-desktop ; sleep 1 ; nohup plasma-desktop
Comment 12 John 2011-11-08 03:42:48 UTC
I also have this problem. It is mostly apparent if you leave the computer on overnight, and come back the next morning to find that nothing is responsive on the desktop at all. I too have found that killing plasma, then loading it again in the same session seems to fix the issue. For now, I cannot leave kopete running while I am away.
Comment 13 Vovochka 2011-11-08 03:59:24 UTC
Version 1.0.80
Using KDE 4.6.00 (4.6.0) "release 6"

openSUSE 11.4
using nouveau as video driver.

After some updates i've noticed that i have no such problem any more.
May be it's still exists but after few hours of notification i have no such problem.
Comment 14 John 2011-11-08 04:12:16 UTC
(In reply to comment #13)
> Kopete
> Version 1.0.80
> Using KDE 4.6.00 (4.6.0) "release 6"
> openSUSE 11.4
> using nouveau as video driver.
> After some updates i've noticed that i have no such problem any more.
> May be it's still exists but after few hours of notification i have no such
> problem.

I am also using OpenSuSE 11.4 with KDE 4.6.0 and Kopete 1.0.80. I am having this issue on 4 different systems all using the nvidia proprietary driver, however a few hours of sitting on a notification does not cause me any problems. I mostly notice this issue when I receive a message sometime in the evening, and I don't see it until the next day.
Comment 15 John 2011-11-08 04:21:25 UTC
Another thing I thought I'd add: this seems to only happen after power management has turned my monitor off. I have 3 desktops and a laptop that are having this problem.
Comment 16 Danilo Cesar Lemes de Paula 2012-05-01 18:13:37 UTC
I believe that entering the screen-saver triggers this problem.
Comment 17 Andreas Hartmetz 2013-07-02 17:25:49 UTC

*** This bug has been marked as a duplicate of bug 314919 ***
Comment 18 Andreas Hartmetz 2013-07-02 22:08:56 UTC
Might not actually be a duplicate of 314919, please reopen if it still occurs after an update that contains the fix from 314919. Not sure yet which version that will be.