[Bug 163243] plasma uses huge amount of CPU time

Alan Braslau alan.braslau at cea.fr
Thu Jun 5 10:23:01 CEST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=163243         




------- Additional Comments From alan.braslau cea fr  2008-06-05 10:23 -------
OK, I stripped my desktop to a bare minimum and logged out and back in (starting from an empty session). The system then responded normally, showing activity as I would have expected. So, indeed, the problem seems to be applications hanging around after previously exploring some of the features of KDE4. I have learned that it is better practice (for me at least) to select "restore manually saved session" in the session manager.

Why python in the original report? I discovered that the culprit was amarok that was left running in the background (but did not appear in the panel before I removed it, as there was no system tray applet). I was unaware that amarok was running a script that spawned many instances of python...

Works for me, too, now.

Maybe it would be useful to have a tool to list (or even to edit) all processes that are active and to be restarted upon login. This would be different from ps, top or krunner that show active processes on the machine regardless of the session.


More information about the Panel-devel mailing list