Bug 274812 - kded4 busy loop with 100% cpu load
Summary: kded4 busy loop with 100% cpu load
Status: RESOLVED DUPLICATE of bug 268038
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 09:05 UTC by AK
Modified: 2011-06-06 15:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description AK 2011-06-03 09:05:20 UTC
Version:           4.6 (using KDE 4.6.2) 
OS:                Linux

After letting kde running for more than 22h, kded4 goes crazy and consumes 100% CPU. 

According to the backtrace, it should be somehow connected with a desktop component. 

Backtrace with gdb gives: 

#0  0x00007f53fc8404e2 in ?? () from /usr/lib/ntrack/modules/ntrack-libnl1.so
#1  0x00007f53fc840a9d in _ntrack_arch_process_data () from /usr/lib/ntrack/modules/ntrack-libnl1.so
#2  0x00007f53fcc7aecb in QNtrack::socketActivated(int) () from /usr/lib/libntrack-qt4.so.1
#3  0x00007f53fcc7b22a in QNtrack::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libntrack-qt4.so.1
#4  0x00007f540ac555f8 in QMetaObject::activate (sender=0x1ae0710, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff32e5c350) at kernel/qobject.cpp:3287
#5  0x00007f540ac9cb7e in QSocketNotifier::activated (this=<value optimized out>, _t1=12) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#6  0x00007f540ac5af4b in QSocketNotifier::event (this=0x1ae0710, e=0x7fff32e5c9e0) at kernel/qsocketnotifier.cpp:317
#7  0x00007f540b8769e4 in QApplicationPrivate::notify_helper (this=0x1958a30, receiver=0x1ae0710, e=0x7fff32e5c9e0) at kernel/qapplication.cpp:4462
#8  0x00007f540b87b3aa in QApplication::notify (this=<value optimized out>, receiver=0x1ae0710, e=0x7fff32e5c9e0) at kernel/qapplication.cpp:4341
#9  0x00007f540c595866 in KApplication::notify (this=0x7fff32e5cc80, receiver=0x1ae0710, event=0x7fff32e5c9e0) at ../../kdeui/kernel/kapplication.cpp:311
#10 0x00007f540ac4049c in QCoreApplication::notifyInternal (this=0x7fff32e5cc80, receiver=0x1ae0710, event=0x7fff32e5c9e0) at kernel/qcoreapplication.cpp:731
#11 0x00007f540ac6ada9 in sendEvent (source=0x195c6a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#12 socketNotifierSourceDispatch (source=0x195c6a0) at kernel/qeventdispatcher_glib.cpp:110
#13 0x00007f540854dbcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f540854e3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f540854e639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f540ac6b3ef in QEventDispatcherGlib::processEvents (this=0x18fe490, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#17 0x00007f540b91ddfe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#18 0x00007f540ac3f882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#19 0x00007f540ac3fabc in QEventLoop::exec (this=0x7fff32e5cc10, flags=...) at kernel/qeventloop.cpp:201
#20 0x00007f540ac43ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#21 0x00007f540d08a135 in kdemain (argc=1, argv=0x7fff32e5d048) at ../../kded/kded.cpp:925
#22 0x00007f540cd0ceff in __libc_start_main (main=0x400730 <main(int, char**)>, argc=1, ubp_av=0x7fff32e5d048, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff32e5d038) at libc-start.c:226
#23 0x0000000000400659 in _start ()



Reproducible: Always

Steps to Reproduce:
Leave kde running for min. 22h straight, sometimes happens after 48h
Comment 1 Christoph Feck 2011-06-06 15:27:52 UTC

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