Version: (using KDE 4.3.4) Installed from: Gentoo Packages Hello, A greate part of kde is block because kded4 use 100% cpu, see the attached file for sysprof profiling.
Created attachment 38830 [details] profile
- Which services do you have installed and running ? Check it on System Settings / Advanced / Service Manager - What is your Qt4 version ? - When does this problem started ? Thanks
- All by default (see my attachement) - qt-4.5.3 - After update of kde
Created attachment 38841 [details] screen shot
Note: Switch to network management backend to Fake Net have seam solve this problem. The version of networkmanager 0.7.1-r6.
This could be related to bug 217371. Thanks
SVN commit 1075552 by dfaure: Fix 100% CPU usage due to a startTimer(0) that was never stopped; this could happen if the timer was started twice, so m_timerId was overwritten, and the first timer ID never recognized. It's much much simpler to use deleteLater: no risk of forgetting the deletion and no risk of timers running forever. It means using QWeakPointer to notice when it got deleted, though. CCMAIL: kretz@kde.org I'm not sure which of the "kded uses 100% cpu" bugs this really fixes; maybe all, or maybe just the one that talks about phonon specifically... Fixed for: 4.4 BUG: 202744 CCBUG: 178228 CCBUG: 184576 CCBUG: 217364 CCBUG: 220047 M +16 -34 hardwaredatabase.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1075552
Available in which version of kde 4.4 for test? kde 4.3.90?
I _just_ committed this today, it would need a time machine to be in the 4.3.90 release from 11 days ago ;). It will be in the next one.
Confirming this behavior using KDE (Platform Version 4.5.95 (4.6 RC2)) If I deactivate networkmanager the problem apparently get solved. Using strace when the kded4 start to eat the CPU shows only a lot of: [pid 2820] poll([{fd=15, events=POLLIN}, {fd=14, events=POLLIN}], 2, -1) = 1 ([{fd=14, revents=POLLIN}]) [pid 2820] clock_gettime(CLOCK_MONOTONIC, {185, 710471893}) = 0 The commit above perhaps solves the problem with the timer, can't test it right now. But I think this bug need to be confirmed.
Still getting this issue on 4.6 final, this time the strace results are different [guilherme@guilherme workspace]$ strace -p 5239 Process 5239 attached - interrupt to quit futex(0x912c35c, FUTEX_WAIT_PRIVATE, 1, NULL] anyone seeing this bug? I will try to made a test case to reproduce this.
*** Bug 217371 has been marked as a duplicate of this bug. ***
I also have 100% of CPU usage of kded4. kde-4.6.0. This happens when IP changes (ADSL connection).
I also have this problem, it happens when I disconnect my network connections. changing backend to fake net didnt help.
If changing the network backend to FakeNet doesn't help, and altering other network things doesn't affect the problem, then you're probably experiencing bug 220047, which happens even if all the kded services are stopped.
I think I could be hitting this bug on Kubuntu Natty. When I come back from hibernation most of the times (if not all.. not sure about coming from sleeping) a kded4 process starts taking 100% CPU time and I lose control of my desktop. I can go to the VTs and kill it and then I can start working on KDE again... but KNetworkManager stops getting any information about wireless networks or GSM networks (I use a GSM dongle) so if I don't want to go down to using konsole and start wvdial to get internet access I have to restart the session... which by the way normally leaves some processes working that I have to kill by hand. I hope the report is usefull. Here's the process I had to kill because it was taking all CPU time, as I said: antoranz 1413 1.5 1.0 230092 21332 ? Rl Apr28 16:27 kdeinit4: kded4 [kdeinit]
This is an strace from the moment when I killed pppd (I had started it by hand, so no user interaction with KNetworkManager involved to start it at all). When I killed pppd kded4 went off as usual. I don't know if it's still related to this bug. What do you think?
*** This bug has been confirmed by popular vote. ***
The bug is seen archlinux with kde4. Networkmanager is thought to be the one who made the kde4d to take up high volume of cpu load. https://bugs.archlinux.org/task/23955
As a comment, I'm not seeing it in kde 4.7 (on kubuntu)... as a matter of fact, I hadn't seen it in quite a while in 4.6.whatever-I-was-on-before-4.7
(In reply to comment #21) > As a comment, I'm not seeing it in kde 4.7 (on kubuntu)... as a matter > of fact, I hadn't seen it in quite a while in > 4.6.whatever-I-was-on-before-4.7 Are you using networkmanager at the same time? The problem could still be seen in archlinux when using networkmanager 0.9.0-1 and kde 4.7.1-1
This is strange, I have never seen this problem happening in my notebook and I use NM with ethernet, wifi and 3G. Even when I used to use NM-0.8 I did not saw this problem, now I am using NM-0.9 and no problems with kded hogging the CPU. Does anyone have any log to support the statement that this problem is in kded's network management module? Are you sure this is not a duplicate of the ntrack bug?
*** Bug 277063 has been marked as a duplicate of this bug. ***
Closing this bug, re-open if it happens again.