Bug 253606

If I understood last nights' IRC discussion correctly, this is probably a problem caused by Solid fstab kded module causing many D-Bus calls.

same problem here.

Thinkpad t30, mandriva cooker, kde4.5.71.

Luca.

have this problem when restarting kde with alt+ctrl+bksp in  4.5.95 (4.6 RC2) under 64bit openSuse

Bug 242909 probably related.

I have a backtrace that might also be related.
Since upgrading to 4.6.0, this seems to be happening rather more frequently.


(gdb) bt
#0  0x00007f9b9ed136b3 in __poll (fds=<value optimized out>, 
    nfds=<value optimized out>, timeout=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f9b9c2cafd4 in g_main_context_poll (context=0x7c6bf0, block=1, 
    dispatch=1, self=<value optimized out>) at gmain.c:2904
#2  g_main_context_iterate (context=0x7c6bf0, block=1, dispatch=1, 
    self=<value optimized out>) at gmain.c:2586
#3  0x00007f9b9c2cb510 in IA__g_main_context_iteration (context=0x7c6bf0, 
    may_block=1) at gmain.c:2654
#4  0x00007f9b9f444a8f in QEventDispatcherGlib::processEvents (this=0x7984d0, 
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#5  0x00007f9b9f419262 in QEventLoop::processEvents (
    this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f9b9f419475 in QEventLoop::exec (this=0x7f9b9215ede0, flags=...)
    at kernel/qeventloop.cpp:201
#7  0x00007f9b9f32c1a4 in QThread::exec (this=<value optimized out>)
    at thread/qthread.cpp:490
#8  0x00007f9b9f3fa918 in QInotifyFileSystemWatcherEngine::run (this=0x786900)
    at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f9b9f32ea1e in QThreadPrivate::start (arg=0x786900)
    at thread/qthread_unix.cpp:285
#10 0x00007f9b9ce21a4f in start_thread (arg=0x7f9b9215f710)
    at pthread_create.c:297
#11 0x00007f9b9ed1c82d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()


and strace shows a /very/ tight loop:

[pid 24272] poll([{fd=14, events=POLLIN}, {fd=12, events=POLLIN}], 2, -1) = 1 ([{fd=12, revents=POLLIN}])

*** Bug 254902 has been marked as a duplicate of this bug. ***

https://bugs.kde.org/show_bug.cgi?id=220047
I've placed traces there that point to fstab module, too.

Created attachment 57934 [details]
view of htop output

This is ~4h after updated to 4.6.1, restarted X with Ctrl+Alt+Backspace.

Platform was openSUSE 11.3 x86_64

for me this was resolved when I upgraded to 4.6.1 and concurrently openSuse 11.4

I think the kded4 part might be Bug 220047.  Don't know about the knotify4 part - I don't get that behaviour.

Certainly Jon Nelson's situation sounds very much like Bug 220047.

This is getting to be a very old bug, going back at least 2 years.
Any change it'll ever have a solution other than "kill it when it kde4/knotify has gone bazerk?"

Needs more info on the problem before it can have a solution -- which kded module is the culprit, with which backtrace. Or a sure way to reproduce the bug for everyone.

See also comment #23 in 220047, looks like recent developments in this bug investigation.

A problem is that it is not repeatable for me.  About once every other week I notice that my cpu usage indicator is showing runaway process(es) and often kded4 or knotify are the culprits.

Must I rebuild kde4/knotify with full debugging information?  What libraries just be retuilt likewise?  How do I determine which module has gone bazerk?  How do I get debugging information on the runaway process as I kill it?

Am experiencing same problem on Kubuntu 11.04 / KDE 4.6.2 (i5-2400 / 8Gb RAM)
kded4 / knotify4 go to 100% CPU intermittently / system becomes sluggish (even though only one or two cores tied up) and unable to log out or shutdown.
Fault occurs 4-5 times per day - am unable to replicate bug.

Came back just now and my CPU was running at 95deg Celcius - not sure why automatic fan speed (BIOS) hadn't kicked up. I'm afraid KDE might be cooking my chips ...

I have just recently started experiencing this too - KDE 4.6.2, Gentoo, 64bit. It may be because I have started using KAlarm - it might be related to knotify not stopping calls to phonon or such from the little I have read online and my small tests.

*** This bug has been marked as a duplicate of bug 220047 ***