Bug 362660

Summary: baloo indexing service crashing
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Jakub <jaktrzeb>
Component: Baloo File DaemonAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aspotashev, christoph, pinak.ahuja
Priority: NOR Keywords: drkonqi
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jakub 2016-05-04 12:10:25 UTC
Application: baloo_file (5.21.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

- git checkout made baloo crash (several thousands of files were modified)
- sometimes it just randomly crash

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f06a49ff780 (LWP 1485))]

Thread 2 (Thread 0x7f0559afb700 (LWP 1669)):
#0  0x00007f06a2517bbd in poll () at /lib64/libc.so.6
#1  0x00007f069ef56e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f069ef56f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f06a3145d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f06a30ecd53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x000000000041531b in  ()
#6  0x00007f06a2f10382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f06a2f1332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f06a15520a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f06a251ffed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f06a49ff780 (LWP 1485)):
[KCrash Handler]
#6  0x00007f06a024225c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x00007f06a37e14cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007f06a37dedc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007f06a37f0949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d453 in  ()
#11 0x000000000041d50d in  ()
#12 0x00007f06a311e73f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#13 0x0000000000427145 in  ()
#14 0x000000000041b6f6 in  ()
#15 0x00007f06a311e73f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#16 0x00007f06a312bf22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007f06a311f8bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007f06a30ef18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007f06a30eee95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007f06a314577d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#21 0x00007f06a3145ad9 in  () at /usr/lib64/libQt5Core.so.5
#22 0x00007f069ef56c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#23 0x00007f069ef56ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f069ef56f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f06a3145d6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007f06a30ecd53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007f06a30f48f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#28 0x000000000040a832 in  ()
#29 0x00007f06a245cb05 in __libc_start_main () at /lib64/libc.so.6
#30 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 359672, bug 355210, bug 353223.

Reported using DrKonqi
Comment 1 Jakub 2016-05-11 07:09:49 UTC
I didnt mention. I'm using crucial bx200 ssd.
Cant confirm if its still crashing. Disabled it.
Comment 2 Christoph Cullmann 2016-09-11 19:23:51 UTC

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