Summary: | Applications freeze while making DCOP calls | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Dima Ryazanov <dima> |
Component: | kded | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | andresbajotierra, grundleborg |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | 3.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dima Ryazanov
2008-05-13 00:46:55 UTC
when I killed Konqueror and Amarok, I saw that I had two instances of kded running, each using up almost 100% of my two CPUs. They had identical stack traces (except for 0x... addresses): #0 QValueListPrivate<int>::contains (this=0x828fd78, x=@0xbfda25f8) at /usr/share/qt3/include/qvaluelist.h:115 #1 0xb639c423 in HomeDirNotify::init () from /usr/lib/kde3/kded_homedirnotify.so #2 0xb639ca7f in HomeDirNotify::toHomeURLList () from /usr/lib/kde3/kded_homedirnotify.so #3 0xb639d250 in HomeDirNotify::FilesRemoved () from /usr/lib/kde3/kded_homedirnotify.so #4 0xb639cf7e in HomeDirNotify::process () from /usr/lib/kde3/kded_homedirnotify.so #5 0xb6a6b0d7 in DCOPClient::receive (this=0x8088458, objId=@0xbfda29cc, fun=@0xbfda29c4, data=@0xbfda29bc, replyType=@0xbfda29b4, replyData=@0xbfda29ac) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:1643 #6 0xb6a6c82b in DCOPProcessInternal (d=0x80a5fd0, opcode=1, key=1, dataReceived=@0xbfda2a88, canPost=true) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:520 #7 0xb6a6cf55 in DCOPProcessMessage (iceConn=0x809e680, clientObject=0x80a5fd0, opcode=1, length=229, replyWait=0x0, replyWaitRet=0xbfda2af4) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:432 #8 0xb6a7d280 in KDE_IceProcessMessages (iceConn=0x809e680, replyWait=0x0, replyReadyRet=0x0) at /build/buildd/kdelibs-3.5.9/./dcop/KDE-ICE/process.c:326 #9 0xb6a635c3 in DCOPClient::processSocketData (this=0x8088458, fd=3) at /build/buildd/kdelibs-3.5.9/./dcop/dcopclient.cpp:2014 #10 0xb6a6cb59 in DCOPClient::qt_invoke (this=0x8088458, _id=2, _o=0xbfda2c98) at ./dcopclient.moc:176 #11 0xb7224893 in QObject::activate_signal (this=0x80ab5d0, clist=0x80bba28, o=0xbfda2c98) at kernel/qobject.cpp:2356 #12 0xb72251aa in QObject::activate_signal (this=0x80ab5d0, signal=2, param=3) at kernel/qobject.cpp:2449 #13 0xb75b1683 in QSocketNotifier::activated (this=0x80ab5d0, t0=3) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #14 0xb724746e in QSocketNotifier::event (this=0x80ab5d0, e=0xbfda2fc8) at kernel/qsocketnotifier.cpp:258 #15 0xb71bbaf0 in QApplication::internalNotify (this=0xbfda3384, receiver=0x80ab5d0, e=0xbfda2fc8) at kernel/qapplication.cpp:2635 #16 0xb71bd91f in QApplication::notify (this=0xbfda3384, receiver=0x80ab5d0, e=0xbfda2fc8) at kernel/qapplication.cpp:2358 #17 0xb78a9a32 in KApplication::notify (this=0xbfda3384, receiver=0x80ab5d0, event=0xbfda2fc8) at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550 #18 0xb714e209 in QApplication::sendEvent (receiver=0x80ab5d0, event=0xbfda2fc8) at ../include/qapplication.h:520 #19 0xb71adee9 in QEventLoop::activateSocketNotifiers (this=0x80ae4d8) at kernel/qeventloop_unix.cpp:578 #20 0xb7162d2b in QEventLoop::processEvents (this=0x80ae4d8, flags=4) at kernel/qeventloop_x11.cpp:383 #21 0xb71d61ce in QEventLoop::enterLoop (this=0x80ae4d8) at kernel/qeventloop.cpp:198 #22 0xb71d5fde in QEventLoop::exec (this=0x80ae4d8) at kernel/qeventloop.cpp:145 #23 0xb71bd699 in QApplication::exec (this=0xbfda3384) at kernel/qapplication.cpp:2758 #24 0xb66d2a38 in kdemain (argc=2, argv=0x8082510) at /build/buildd/kdelibs-3.5.9/./kded/kded.cpp:961 #25 0xb7f56454 in kdeinitmain (argc=2, argv=0x8082510) at kded_dummy.cpp:3 #26 0x0804e6ff in launch (argc=2, _name=0x80510b9 "kded", args=0x80510dc "", cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051034 "0") at /build/buildd/kdelibs-3.5.9/./kinit/kinit.cpp:673 #27 0x08050497 in main (argc=5, argv=0xbfda3844, envp=0xbfda385c) at /build/buildd/kdelibs-3.5.9/./kinit/kinit.cpp:1855 #28 0xb7cb4050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #29 0x0804bba1 in _start () Oops, sorry, didn't realize that I picked a Kopete-specific component. I should also add - it started working fine after killing kded. I upgraded to KDE 4.1 - and it's even worse. I have to kill kded every time I start KDE, and even then, it doesn't always help. Any news on this ? Also, KDE4 doesn't use DCOP but DBUS. You were probably experiencing a different bug. Thanks Marking as NEEDSINF Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |