Version: (using KDE 4.2.3) OS: Linux Installed from: Gentoo Packages Now randomly crash KTorrent and kded4. I don't have the backtrace for KTorrent but have for kded4. Service KDE (kded4) crashed and caused the signal 11 (SIGSEGV). 0x00007f4bb750e8a0 in __nanosleep_nocancel () from /lib/libc.so.6 Current language: auto; currently c Thread 1 (Thread 0x7f4bbbeea750 (LWP 4110)): [KCrash Handler] #5 QUtf8Codec::convertFromUnicode (this=<value optimized out>, uc=0x142fa6a, len=24383488, state=0x0) at codecs/qutfcodec.cpp:82 #6 0x00007f4bba6c6798 in QTextCodec::fromUnicode (this=0x7f4ba560eb08, str=<value optimized out>) at codecs/qtextcodec.cpp:1189 #7 0x00007f4bba607c91 in QString::toLocal8Bit (this=0x1475620) at tools/qstring.cpp:3358 #8 0x00007f4bba63ee99 in locale_encode (f=@0x7f4ba560eb08) at io/qfile.cpp:70 #9 0x00007f4bba63ed1a in QFile::encodeName (fileName=@0x7f4ba560eb08) at io/qfile.cpp:484 #10 0x00007f4bbb76ea8f in KDirWatchPrivate::useINotify (this=0x13dbfe0, e=0x14755f8) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kio/kio/kdirwatch.cpp:586 #11 0x00007f4bbb7721eb in KDirWatchPrivate::inotifyEventReceived (this=0x13dbfe0) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kio/kio/kdirwatch.cpp:311 #12 0x00007f4bbb774508 in KDirWatchPrivate::qt_metacall (this=0x13dbfe0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc3f31850) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs_build/kio/kdirwatch_p.moc:75 #13 0x00007f4bba6aeed5 in QMetaObject::activate (sender=0x13fc3d0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x3ca616a) at kernel/qobject.cpp:3108 #14 0x00007f4bba6e0d4e in QSocketNotifier::activated (this=0x0, _t1=9) at .moc/release-shared/moc_qsocketnotifier.cpp:83 #15 0x00007f4bba6b4ce3 in QSocketNotifier::event (this=0x13fc3d0, e=0x7fffc3f31e20) at kernel/qsocketnotifier.cpp:316 #16 0x00007f4bb927881d in QApplicationPrivate::notify_helper (this=0x12f6820, receiver=0x13fc3d0, e=0x7fffc3f31e20) at kernel/qapplication.cpp:4057 #17 0x00007f4bb92810ea in QApplication::notify (this=0x7fffc3f32140, receiver=0x13fc3d0, e=0x7fffc3f31e20) at kernel/qapplication.cpp:4022 #18 0x00007f4bbb250bab in KApplication::notify (this=0x7fffc3f32140, receiver=0x13fc3d0, event=0x7fffc3f31e20) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kdeui/kernel/kapplication.cpp:307 #19 0x00007f4bba69cce3 in QCoreApplication::notifyInternal (this=0x7fffc3f32140, receiver=0x13fc3d0, event=0x7fffc3f31e20) at kernel/qcoreapplication.cpp:606 #20 0x00007f4bba6c1e89 in socketNotifierSourceDispatch (source=0x12f95d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 0x00007f4bb51da7b1 in IA__g_main_context_dispatch (context=0x12f9480) at gmain.c:1814 #22 0x00007f4bb51dddd0 in g_main_context_iterate (context=0x12f9480, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2448 #23 0x00007f4bb51ddf6c in IA__g_main_context_iteration (context=0x12f9480, may_block=1) at gmain.c:2511 #24 0x00007f4bba6c1c1f in QEventDispatcherGlib::processEvents (this=0x12f67f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324 #25 0x00007f4bb92fda5f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007f4bba69b6e2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1007476672}) at kernel/qeventloop.cpp:149 #27 0x00007f4bba69b875 in QEventLoop::exec (this=0x7fffc3f32080, flags={i = -1007476592}) at kernel/qeventloop.cpp:196 #28 0x00007f4bba69d874 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00007f4bbbb0ff52 in kdemain (argc=1, argv=0x7fffc3f324f8) at /var/tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kded/kded.cpp:937 #30 0x00007f4bb748d5c6 in __libc_start_main (main=0x400960 <main>, argc=1, ubp_av=0x7fffc3f324f8, init=0x400990 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffc3f324e8) at libc-start.c:226 #31 0x0000000000400899 in _start ()
It would be interesting to know the version of Qt in use and what the file name in question was (which may be possible to retrieve from future crashes by investigating frame 10 (KDirWatchPrivate::useINotify) in gdb to print out the filename). Seems to me like a Qt bug though, perhaps already fixed in 4.5 (assuming you're using an older Qt release).
I don't reproduce this bug now. It was be for me only once. Maybe I was using old Qt. Now I have kde-4.2.4 x11-libs/qt-3.3.8b-r1 x11-libs/qt-core-4.5.1 Do you want continue to support this bug or may close it? Can you get me instructions what can I do to help you in this bug or to determine is this bug because i use old Qt?
Seems to me like a KDirWatch bug rather than a Qt bug (with KDirWatch passing a deleted QString to Qt), but anyway - not much we can do about an unreproduced crash. Please reopen if it happens again, thanks.