Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Baloo crashes after a while, no matter what I'm doing. - Unusual behavior I noticed: After a reboot, the desktop gets incrementally slower to the point of not being usable. Baloo takes more and more memory. After a long while, baloo crashes. Then the desktop becomes usable again. The crash can be reproduced every time. -- 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 0x7f4f10ede780 (LWP 23132))] Thread 2 (Thread 0x7f4dc5ee3700 (LWP 23137)): #0 0x00007f4f0ea14648 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x00007f4f0e9ffc09 in poll () at /lib64/libc.so.6 #2 0x00007f4f0b440e64 in () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f4f0b440f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f4f0f62dd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007f4f0f5d4d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #6 0x000000000041531b in () #7 0x00007f4f0f3f8382 in () at /usr/lib64/libQt5Core.so.5 #8 0x00007f4f0f3fb32f in () at /usr/lib64/libQt5Core.so.5 #9 0x00007f4f0da3c0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x00007f4f0ea0802d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4f10ede780 (LWP 23132)): [KCrash Handler] #6 0x00007f4f0c72c25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so #7 0x00007f4f0fcc94cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x00007f4f0fcc6dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x00007f4f0fcd8949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x000000000041d453 in () #11 0x000000000041d50d in () #12 0x00007f4f0f60673f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x0000000000427145 in () #14 0x000000000041b6f6 in () #15 0x00007f4f0f60673f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x00007f4f0f613f22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x00007f4f0f6078bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x00007f4f0f5d718d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x00007f4f0f5d6e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x00007f4f0f62d77d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #21 0x00007f4f0f62dad9 in () at /usr/lib64/libQt5Core.so.5 #22 0x00007f4f0b440c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #23 0x00007f4f0b440ed8 in () at /usr/lib64/libglib-2.0.so.0 #24 0x00007f4f0b440f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #25 0x00007f4f0f62dd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #26 0x00007f4f0f5d4d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #27 0x00007f4f0f5dc8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #28 0x000000000040a832 in () #29 0x00007f4f0e944b25 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
I rebooted today. Uptime was about 8 minutes when the crash happened. The desktop didn't become slow, I forgot to check memory usage.
*** Bug 368193 has been marked as a duplicate of this bug. ***
*** Bug 368243 has been marked as a duplicate of this bug. ***
*** Bug 367212 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 352984 ***