Bug 425266 - baloo_file_extractor crashing repeatedly when indexing starts
Summary: baloo_file_extractor crashing repeatedly when indexing starts
Status: RESOLVED DUPLICATE of bug 405284
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.68.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-08-12 16:36 UTC by Ben Li
Modified: 2020-10-26 16:02 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Li 2020-08-12 16:36:28 UTC
Application: baloo_file_extractor (5.68.0)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.1 LTS

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

Crashes every time indexing starts. I have not yet tried re-indexing completely in case there's useful state to extract. 

The only file showing as failed is an innocuous looking text file from the chromium snap: /home/bli/snap/chromium/common/chromium/pnacl/0.57.44.2492/_platform_specific/x86_64/pnacl_public_pnacl_json

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1576056f80 (LWP 2137))]

Thread 3 (Thread 0x7f157494c700 (LWP 2148)):
#0  __GI___libc_read (nbytes=16, buf=0x7f157494bb60, fd=8) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=8, buf=0x7f157494bb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x00007f15780a289f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f1578059cfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f157805a152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f157805a2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f157943d583 in QEventDispatcherGlib::processEvents (this=0x7f1568000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#7  0x00007f15793e44db in QEventLoop::exec (this=this@entry=0x7f157494bd70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#8  0x00007f157921c785 in QThread::exec (this=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#9  0x00007f157a447efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007f157921d9d2 in QThreadPrivate::start (arg=0x7f157a4cad80) at thread/qthread_unix.cpp:361
#11 0x00007f1578919609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#12 0x00007f1578eac103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f15751a5700 (LWP 2143)):
#0  0x00007f1578e9f96f in __GI___poll (fds=0x7f15751a4ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f1577fe7c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f1577fe990a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f15759a9298 in QXcbEventQueue::run (this=0x5630bb6f3580) at qxcbeventqueue.cpp:228
#4  0x00007f157921d9d2 in QThreadPrivate::start (arg=0x5630bb6f3580) at thread/qthread_unix.cpp:361
#5  0x00007f1578919609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f1578eac103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f1576056f80 (LWP 2137)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f1578daf859 in __GI_abort () at abort.c:79
#8  0x00007f1578adaa83 in mdb_assert_fail (env=0x5630bb776590, expr_txt=expr_txt@entry=0x7f1578add02f "rc == 0", func=func@entry=0x7f1578add978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7f1578add010 "mdb.c") at mdb.c:1542
#9  0x00007f1578acf6d5 in mdb_page_dirty (mp=<optimized out>, txn=0x5630bb7780c0) at mdb.c:2114
#10 mdb_page_dirty (txn=0x5630bb7780c0, mp=<optimized out>) at mdb.c:2114
#11 0x00007f1578ad0966 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffd3e3c7588, mc=<optimized out>) at mdb.c:2308
#12 0x00007f1578ad0ba3 in mdb_page_touch (mc=mc@entry=0x7ffd3e3c7a10) at mdb.c:2495
#13 0x00007f1578ad27ec in mdb_cursor_touch (mc=mc@entry=0x7ffd3e3c7a10) at mdb.c:6523
#14 0x00007f1578ad6a0f in mdb_cursor_del (flags=32, mc=0x7ffd3e3c7a10) at mdb.c:7081
#15 mdb_cursor_del (mc=0x7ffd3e3c7a10, flags=32) at mdb.c:7063
#16 0x00007f1578ad82e3 in mdb_del0 (txn=0x5630bb7780c0, dbi=<optimized out>, key=key@entry=0x7ffd3e3c7e00, data=<optimized out>, flags=32, flags@entry=0) at mdb.c:8571
#17 0x00007f1578ad863e in mdb_del (txn=<optimized out>, dbi=<optimized out>, key=key@entry=0x7ffd3e3c7e00, data=<optimized out>, data@entry=0x0) at mdb.c:8531
#18 0x00007f157a4f8af9 in Baloo::DocumentDB::del (this=this@entry=0x7ffd3e3c7f50, docId=<optimized out>, docId@entry=22008726684696631) at ./src/engine/documentdb.cpp:118
#19 0x00007f157a52b253 in Baloo::WriteTransaction::removeDocument (this=0x5630bb776510, id=id@entry=22008726684696631) at ./src/engine/writetransaction.cpp:130
#20 0x00007f157a51c987 in Baloo::Transaction::removeDocument (this=<optimized out>, id=id@entry=22008726684696631) at ./src/engine/transaction.cpp:266
#21 0x00005630b9fa559a in Baloo::App::processNextFile (this=0x7ffd3e3c87f0) at ./src/file/extractor/app.cpp:106
#22 0x00007f157941e5b6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e3c81e0, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#23 QSingleShotTimer::timerEvent (this=0x5630bb776740) at kernel/qtimer.cpp:318
#24 0x00007f1579411cf5 in QObject::event (this=0x5630bb776740, e=<optimized out>) at kernel/qobject.cpp:1283
#25 0x00007f1579dfda66 in QApplicationPrivate::notify_helper (this=this@entry=0x5630bb6f0140, receiver=receiver@entry=0x5630bb776740, e=e@entry=0x7ffd3e3c8500) at kernel/qapplication.cpp:3700
#26 0x00007f1579e070f0 in QApplication::notify (this=0x7ffd3e3c87e0, receiver=0x5630bb776740, e=0x7ffd3e3c8500) at kernel/qapplication.cpp:3446
#27 0x00007f15793e593a in QCoreApplication::notifyInternal2 (receiver=0x5630bb776740, event=0x7ffd3e3c8500) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:142
#28 0x00007f157943c8b0 in QTimerInfoList::activateTimers (this=0x5630bb74ae80) at kernel/qtimerinfo_unix.cpp:643
#29 0x00007f157943d19c in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182
#30 0x00007f1578059fbd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f157805a240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f157805a2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f157943d565 in QEventDispatcherGlib::processEvents (this=0x5630bb724150, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#34 0x00007f15793e44db in QEventLoop::exec (this=this@entry=0x7ffd3e3c8740, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#35 0x00007f15793ec246 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#36 0x00005630b9fa37d4 in main (argc=<optimized out>, argv=<optimized out>) at ./src/file/extractor/main.cpp:59
[Inferior 1 (process 2137) detached]

The reporter indicates this bug may be a duplicate of or related to bug 405284.

Possible duplicates by query: bug 425142, bug 425017, bug 424911, bug 423951, bug 423222.

Reported using DrKonqi
Comment 1 Thiago Sueto 2020-09-03 02:42:51 UTC
Hello, could you enable the debug repositories for Ubuntu?
You can do so by following this: https://wiki.ubuntu.com/Debug%20Symbol%20Packages

After that, please install kubuntu-debug-installer and reproduce this bug again, using Dr. Konqi to fetch the required debug symbols.
Comment 2 Ben Li 2020-09-03 16:19:33 UTC
Is there a specific part of the trace that needs to be improved? I've already gone through that process, and Dr. Konqi does not suggest any additional debug symbol packages.
Comment 3 Thiago Sueto 2020-09-03 16:32:31 UTC
That was my mistake. sorry for the inconvenience. Still a rookie triager.
I just asked another contributor today and most often just the debug symbols for the thread marked with KCrash Handler are sufficient.
Comment 4 Nate Graham 2020-10-26 16:02:28 UTC

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