Application: nepomukservicestub (0.2) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.6.3 Operating System: Linux 2.6.34-12-desktop i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: - Custom settings of the application: Nepomuk and Strigi both enabled Indexing of removable media is deactivated Strigi seems to have problems in indexing some folders containing an mp4 file -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Aborted [Current thread is 1 (Thread 0xb5851710 (LWP 13895))] Thread 2 (Thread 0xb1b6bb70 (LWP 13915)): [KCrash Handler] #7 0xffffe424 in __kernel_vsyscall () #8 0xb61587ff in raise () from /lib/libc.so.6 #9 0xb615a140 in abort () from /lib/libc.so.6 #10 0xb6194fd7 in __libc_message () from /lib/libc.so.6 #11 0xb619affb in malloc_printerr () from /lib/libc.so.6 #12 0xb619bd7b in _int_free () from /lib/libc.so.6 #13 0xb619fadd in free () from /lib/libc.so.6 #14 0xb761af3b in qFree (ptr=0x84d0bf8) at global/qmalloc.cpp:60 #15 0xb766c4a2 in QString::free (d=0x84d0bf8) at tools/qstring.cpp:1108 #16 0xb766ca80 in QString::operator= (this=0x811484c, other=@0x86a8ec8) at tools/qstring.cpp:1282 #17 0xb2c41dbc in Nepomuk::IndexScheduler::updateDir (this=0x8114820, dir=..., analyzer=0xb1b6b30c, flags=...) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:337 #18 0xb2c42858 in Nepomuk::IndexScheduler::updateDir (this=0x8114820, dir=..., analyzer=0xb1b6b30c, flags=...) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:422 #19 0xb2c42858 in Nepomuk::IndexScheduler::updateDir (this=0x8114820, dir=..., analyzer=0xb1b6b30c, flags=...) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:422 #20 0xb2c42858 in Nepomuk::IndexScheduler::updateDir (this=0x8114820, dir=..., analyzer=0xb1b6b30c, flags=...) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:422 #21 0xb2c42dca in Nepomuk::IndexScheduler::run (this=0x8114820) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/services/strigi/indexscheduler.cpp:314 #22 0xb762004f in QThreadPrivate::start (arg=0x8114820) at thread/qthread_unix.cpp:248 #23 0xb75a6b25 in start_thread () from /lib/libpthread.so.0 #24 0xb620046e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5851710 (LWP 13895)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb620e5b3 in __lll_lock_wait_private () from /lib/libc.so.6 #2 0xb61a135f in _L_lock_10260 () from /lib/libc.so.6 #3 0xb619fad6 in free () from /lib/libc.so.6 #4 0xb634a98f in operator delete(void*) () from /usr/lib/libstdc++.so.6 #5 0xb77460e2 in QEventDispatcherGlib::unregisterSocketNotifier (this=0x8053648, notifier=0x80b1730) at kernel/qeventdispatcher_glib.cpp:493 #6 0xb7734248 in QSocketNotifier::setEnabled (this=0x80b1730, enable=false) at kernel/qsocketnotifier.cpp:298 #7 0xb77457ce in socketNotifierSourceCheck (source=0x8069ea8) at kernel/qeventdispatcher_glib.cpp:92 #8 0xb605b7d0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #9 0xb605c108 in ?? () from /usr/lib/libglib-2.0.so.0 #10 0xb605c60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #11 0xb7745d4b in QEventDispatcherGlib::processEvents (this=0x8053648, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #12 0xb657119a in QGuiEventDispatcherGlib::processEvents (this=0x8053648, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #13 0xb771911d in QEventLoop::processEvents (this=0xbfa69864, flags=...) at kernel/qeventloop.cpp:149 #14 0xb7719319 in QEventLoop::exec (this=0xbfa69864, flags=...) at kernel/qeventloop.cpp:201 #15 0xb771dc70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #16 0xb64be164 in QApplication::exec () at kernel/qapplication.cpp:3581 #17 0x0804b055 in main (argc=) at /usr/src/debug/kdebase-runtime-4.5.0/nepomuk/servicestub/main.cpp:152 This bug may be a duplicate of or related to bug 230592. Possible duplicates by query: bug 242656, bug 240783. Reported using DrKonqi
could it be possible that you run it with valgrind ? ( to have better infos about the memory issue )
Created attachment 50922 [details] Another crashlog Here is another crashlog, reported by DrKonqi. Can you please indicate me how to launch nepomukservice via valgrind?
*** This bug has been marked as a duplicate of bug 248244 ***