Bug 204183 - plasma-desktop cpu usage escalates until system unresponsive (seems Kickoff related)
Summary: plasma-desktop cpu usage escalates until system unresponsive (seems Kickoff r...
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-kickoff (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-17 16:29 UTC by Patrick Shanahan
Modified: 2010-05-21 04:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Shanahan 2009-08-17 16:29:50 UTC
Version:           kdebase4-workspace-4.3.0-320.1 (using KDE 4.3.0)
Compiler:          gcc-4.4-3.4 
OS:                Linux
Installed from:    SuSE RPMs

plasma-desktop uses more and more cpu until the desktop becomes quite sluggish.  Temporary solution is to kill plasma-desktop and restart it.  This is very annoying.

see openSUSE bug report #529358:
 https://bugzilla.novell.com/show_bug.cgi?id=529358

I have logs of plasma-desktop cpu usage at 15 minute intervals on my x86_64 dual system:
 http://wahoo.no-ip.org/~pat/plasma-desktop-cpu.txt

I created a new user and experienced same problem.

I disabled *all* the plasmoids except taskmanager, application aluncher, device notifier, folder view, lock/logout, pager, show widget dashboard and system tray and turned off composting and desktop effects, all to no avail.
Comment 1 Dario Andres 2009-08-17 16:53:47 UTC
- Does the cpu usage stop if you remove and readd the System Tray ? (like bug 204070)
Thanks
Comment 2 Patrick Shanahan 2009-08-17 17:17:34 UTC
didn't try that, will now.  Will advise
Comment 3 Patrick Shanahan 2009-08-17 18:15:29 UTC
Appears removing "System Tray" and then replacing it reduced cpu usage and that usage is remaining lower, about 6.4%.  

I looked at 204070, but I have nothing hidden.

Is there a problem with "System Tray"?
Comment 4 Dario Andres 2009-08-17 18:19:07 UTC
If you have nothing hidden, then it is a different issue. The system tray has no problems as far as I know. Regards
Comment 5 Patrick Shanahan 2009-08-17 18:35:15 UTC
Update:  The problem is still present.  Removing "System Tray" and "Taskbar"
and replacing them "did not solve proble".  CPU usage is again escalating.
Comment 6 Dario Andres 2009-08-17 18:46:42 UTC
Try removing the widgets your currently have one by one (but not readding them), and after each removal measure the Plasma CPU usage to see if it keeps low or if it raises again. Hopefully we can identify the culprit.
Thanks
Comment 7 Patrick Shanahan 2009-08-18 02:20:11 UTC
I have only removed "Application Launcher" (new style), and the cpu usage (also X cpu usage) has dropped remarkably.  After a system restart (new kernel) and today's "zypper dup", cpu usage for plasma-desktop is 1.7% and has dropped steadily from 4.6% at start.

I will reinstall "Application Launcher" to confirm, and also try the old style for comparison and advise result.  I will also try "Application Launcher" on the desktop rather than the "System Tray".

tks,
Comment 8 Dario Andres 2009-09-04 16:57:23 UTC
Waiting for the results of the tests.. Thanks
Comment 9 Patrick Shanahan 2009-09-08 18:18:13 UTC
the "Kickoff" style application launcher still escalates cpu usage.  Traditional style appears to use ~1.4% after a period of decline following startup.

openSUSE 11.2/M7
Comment 10 Dario Andres 2009-09-09 20:12:35 UTC
Thanks
Comment 11 Patrick Shanahan 2009-09-09 20:29:51 UTC
Observed a condition that may contribute.  I gain "activities" that I have not
created myself w/o any notice.  I can go to the cashew and zoom out and see
activities that I did not know existed.  Deleting/removing these activities is
*very* slow.
Comment 12 Aaron J. Seigo 2010-05-21 04:39:00 UTC
the kickoff-eating-cpu issue was reported elsewhere and fixed, comment #11 is not relevant (and due to per-virtual-desktop-containments and/or separate dashboard toggling)