[Bug 163243] plasma uses huge amount of CPU time

[Sebastian Sauer]

------- 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 mail dipe org  2008-06-05 16:55 -------
Hi Alan,

first thanks for your additional feedback. It is for sure not a prob to don't note that a reported thing may related to another already reported thing and it's for sure also not a problem to have multiple reports about the same issue since that shows us very good how much users are affected by the problem what in turn may help to prioritize things a bit.

Re "No single detail provided"; well, I was refering here to _for_us_ useful details. Also it's not a problem if they are not provided since not everybody may know what useful informations may are. In that case the normal way would be to just ask for them and then try to look if the report is probably related to another report, if the problem can be reproduced by us and how to fix it.

But there are some reports that are just not worth to spend time with. Let's look why I was believing that your report was falling into that category;

"I am suprised by plasma's hunger. Running almost nothing (useful that is) still eats up lots of CPU time. "

Ok, this let's us know that "plasma uses huge amount of CPU time" on your system. Indend a very useful information but that alone doesn't help us to address it.
 
"I've tried removing all plasmoids, all panels, no background, no windows, no effects."

This could be another very useful information if that wouldn't open multiple additional questions like;
* How did you removed them? (no background == no background-image?)
* Did you restart in between (aka after removing them)?
* What plasmoids got removed?

"Switching to another virtual console still reports lots of plasma and python activity."

* So, plasma was still running and you switched to another virtual console (not virtual desktop) and did a "top"?
* What plasma activity?
* What python activity?
* What means "lots"?

"I suspect that even with no productive work going on, the power is still there... "

Without question I suspect the same.
 
"This CPU bloat is almost like Windows!"

Yay. And that's where the report turned from the "reask" into the "not-worth-to-spend-time-with" category. Please consider that you did report a *bug* here and it's *not* anybody's motivation to let your CPU bleed but to *fix* the bug.

"Doing what? I'll try removing EVERYTHING again and start a new session, because there may be active processes left hanging around, I suspect."
 
Yes, this would great :) Also it would be still great to have more details. So, after restarting the session (without any plasmoids enabled) is the CPU-usage still that high? If not, then one of the plasmoids was responsible and we are one step closer to assume that you did run into bug #163186 as well. To be sure we could try to isolate the plasmoid that is responsible for it but in any case, once we are there, I could try to reproduce the problem on my system and on success (and if it's not related to bug #16318 at all) it would make it much easier to find a solution :)

"Basic KDE use must not load down the machine."

Do you really believe anybody wouldn't agree there? Well, you reported a *bug* and per definition a bug is an unwanted thing (well, at least for us :) that needs to be fixed and it does not help (your report and therefore us) to assume we just collect bugreports to don't fix them.

But as sayed: please reopen the report and provide us some more details if you like (I named some of the questions above already) and please just assume that we try to fix your bug rather then believing it's a wanted "feature" to bleed your CPU ;)