Ubuntu

kded hogs cpu

Bug #120893 reported by Robert Persson
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

On a couple of occasions today I have found that kded has been hogging between 95% and 175% cpu (yes, that's what top was telling me - it's something to do with hyperthreading I expect) and I have had to force it to shut. On one of those occasions a normal kill wouldn't do the job so I had to kill -9 it. I have been experiencing very sluggish performance since switching from Gnome to KDE, so this problem may have been occurring a lot more frequently than I have been aware of.

Another thing that happened a couple of times today, although I don't know if it is connected, has been that the machine started thrashing to the point of being completely unresponsive and forcing me to press the reset button on the case. I know that swap was enabled on those occasions because the System Monitor applet told me so. I remember noticing, on one of the occasions on which I had to kill kded, that kded had taken up about 170Mb or so of swap space.

Revision history for this message
Jason Liquorish (jason-liquorish) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

Revision history for this message
Robert Persson (ireneshusband) wrote :

Please tell me how I can obtain the kind of information you would need. What should I do? What should I look out for?

Would strace be the right tool to use? If so, should I just try to run it when kded has already gone bananas, or should I set it running when I log in? I haven't experienced the fault again since I reported it, so would leaving strace running all the time produce an unbearably huge log file?

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I'm experiencing the same problem on latest Kubuntu Gutsy. Sometimes kded eats all cpu and I have to kill it. The problem is that it breaks automount.

What kind of debug can we provide for this?

Revision history for this message
Robert Persson (ireneshusband) wrote :

Strangely, I have not experienced the runaway kde recently, but I have found that at some point in the last few weeks automount completely stopped working. Are you saying that these two problems might be related?

 What has also been happening since I reported this bug has been that fairly soon after I log in I get a message telling me that kded has crashed. Sometimes this happens twice in within the first—I dunno—perhaps twenty minutes or so. Occasionally it happens again later on. But it never fails to happen straight after login.

What also happens around the time that this happens for the first time at login, although it rarely happens absolutely simultaneously with it, is that I get a message box saying something about processing the file "trash:/" (I can't remember the exact message, but I can make a note of it next time I log in if it is needed). This message box hangs around for several seconds, during which time neither the remainder of the kde panel nor the desktop gets populated with widgets and files. I don't know if this is yet another bug, but I mention it here just in case it is part of the same problem.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.