Bug 283314 - Crash in kinotify destructor
Summary: Crash in kinotify destructor
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: filewatch (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-04 12:52 UTC by romain
Modified: 2013-06-05 22:46 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description romain 2011-10-04 12:52:58 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Ubuntu oneiric (development branch)

-- Information about the crash:
Nepomuk crash all time when he is indexing files. 
this occurs since KDE 4.6 in this computer, but i haven't this problem with my other computer.

-- Backtrace:
Application: Jeton du service Nepomuk (nepomukservicestub), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fe497f02780 (LWP 3449))]

Thread 2 (Thread 0x7fe487b29700 (LWP 3580)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007fe4955029df in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007fe495500d71 in __GI___libc_free (mem=0x7fe49581e1c0) at malloc.c:3736
#3  0x00007fe497a17665 in socketNotifierSourceCheck (source=0x2691a00) at kernel/qeventdispatcher_glib.cpp:92
#4  0x00007fe49478c734 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe49478cf82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fe49478d429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007fe497a17ed6 in QEventDispatcherGlib::processEvents (this=0x268fcc0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#8  0x00007fe4979ebcf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#9  0x00007fe4979ebef7 in QEventLoop::exec (this=0x7fe487b28dd0, flags=...) at kernel/qeventloop.cpp:201
#10 0x00007fe49790327f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#11 0x00007fe4979cecbf in QInotifyFileSystemWatcherEngine::run (this=0x26874c0) at io/qfilesystemwatcher_inotify.cpp:248
#12 0x00007fe497905d05 in QThreadPrivate::start (arg=0x26874c0) at thread/qthread_unix.cpp:331
#13 0x00007fe49526eefc in start_thread (arg=0x7fe487b29700) at pthread_create.c:304
#14 0x00007fe49556589d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#15 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe497f02780 (LWP 3449)):
[KCrash Handler]
#6  0x00007fe4954fcdc4 in malloc_consolidate (av=0x7fe49581e1c0) at malloc.c:5161
#7  0x00007fe4954fd659 in malloc_consolidate (av=0x7fe49581e1c0) at malloc.c:5115
#8  _int_free (av=0x7fe49581e1c0, p=<optimized out>) at malloc.c:5034
#9  0x00007fe495500d7c in __GI___libc_free (mem=<optimized out>) at malloc.c:3738
#10 0x00007fe4887c0899 in ~QList (this=0x263c5e8, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:719
#11 ~QQueue (this=0x263c5e8, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qqueue.h:58
#12 ~Private (this=0x263c5d0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/kinotify.cpp:74
#13 KInotify::~KInotify (this=0x25f9b10, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/kinotify.cpp:241
#14 0x00007fe4887b5e73 in ~IgnoringKInotify (this=0x25f9b10, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/nepomukfilewatch.cpp:78
#15 (anonymous namespace)::IgnoringKInotify::~IgnoringKInotify (this=<optimized out>, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/nepomukfilewatch.cpp:80
#16 0x00007fe4979fed75 in QObjectPrivate::deleteChildren (this=0x25af2d0) at kernel/qobject.cpp:1955
#17 0x00007fe497a04349 in QObject::~QObject (this=0x25b3f20, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#18 0x00007fe4887b613a in Nepomuk::FileWatch::~FileWatch (this=0x25b3f20, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/nepomukfilewatch.cpp:174
#19 0x00007fe4887b6199 in Nepomuk::FileWatch::~FileWatch (this=0x25b3f20, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/nepomukfilewatch.cpp:179
#20 0x00007fe4979fed75 in QObjectPrivate::deleteChildren (this=0x2549d30) at kernel/qobject.cpp:1955
#21 0x00007fe497a04349 in QObject::~QObject (this=0x2547de0, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#22 0x0000000000404419 in Nepomuk::ServiceControl::~ServiceControl (this=0x2547de0, __in_chrg=<optimized out>) at ../../../nepomuk/servicestub/servicecontrol.cpp:39
#23 0x00007fe4979fed75 in QObjectPrivate::deleteChildren (this=0x241d680) at kernel/qobject.cpp:1955
#24 0x00007fe497a04349 in QObject::~QObject (this=0x7fff1fb0a230, __in_chrg=<optimized out>) at kernel/qobject.cpp:946
#25 0x00007fe495d2ff87 in QApplication::~QApplication (this=0x7fff1fb0a230, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1093
#26 0x0000000000403a4d in main (argc=2, argv=0x7fff1fb0a6d8) at ../../../nepomuk/servicestub/main.cpp:102

This bug may be a duplicate of or related to bug 281548.

Possible duplicates by query: bug 281548, bug 280828.

Reported using DrKonqi
Comment 1 Sebastian Trueg 2011-10-04 13:01:59 UTC
Does this happen when shutting down the system or during normal operation?
Comment 2 romain 2011-10-04 13:11:20 UTC
During the both.

Le 04/10/2011 15:02, Sebastian Trueg a écrit :
> https://bugs.kde.org/show_bug.cgi?id=283314
>
>
> Sebastian Trueg<trueg@kde.org>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |ASSIGNED
>                   CC|                            |trueg@kde.org
>       Ever Confirmed|0                           |1
>
>
>
>
> --- Comment #1 from Sebastian Trueg<trueg kde org>   2011-10-04 13:01:59 ---
> Does this happen when shutting down the system or during normal operation?
>
Comment 3 Simeon Bird 2013-06-05 22:46:32 UTC
This should be fixed now, since we don't use QQueue, and we explicitly empty the dirIterator that replaced it on destruction.