https://bugs.kde.org/show_bug.cgi?id=445773

--- Comment #1 from David Kredba <nheghathivhis...@gmail.com> ---
After I moved the file outside the FS, it crashes again without any file being
indexed before the crash.
'balooctl monitor':
Starting
Checking for stale index entries
Indexing file content

[KCrash Handler]
#4  0x00007fa691c2b4e3 in mdb_midl_xmerge (idl=idl@entry=0x7f6613db4018,
merge=merge@entry=0x7f66cc4a9010) at midl.c:207
#5  0x00007fa691c22697 in mdb_page_alloc (num=num@entry=233,
mp=mp@entry=0x7ffe42696b60, mc=<optimized out>, mc=<optimized out>) at
mdb.c:2280
#6  0x00007fa691c24af7 in mdb_page_new (mp=<synthetic pointer>, num=233,
flags=4, mc=0x7ffe42696cd0) at mdb.c:7193
#7  mdb_node_add (mc=mc@entry=0x7ffe42696cd0, indx=<optimized out>,
key=key@entry=0x7ffe426970c0, data=0x7ffe426970d0, pgno=pgno@entry=0, flags=0)
at mdb.c:7335
#8  0x00007fa691c28189 in mdb_cursor_put (mc=mc@entry=0x7ffe42696cd0,
key=key@entry=0x7ffe426970c0, data=data@entry=0x7ffe426970d0,
flags=flags@entry=0) at mdb.c:6960
#9  0x00007fa691c2a961 in mdb_put (txn=0x56039916d740, dbi=<optimized out>,
key=0x7ffe426970c0, data=0x7ffe426970d0, flags=0) at mdb.c:9045
#10 0x00007fa692e3cddb in Baloo::PositionDB::put
(this=this@entry=0x7ffe426971c0, term=..., list=...) at
/var/tmp/portage/kde-frameworks/baloo-5.88.0/work/baloo-5.88.0/src/engine/positiondb.cpp:69
#11 0x00007fa692e4f9a0 in Baloo::WriteTransaction::commit (this=<optimized
out>) at
/var/tmp/portage/kde-frameworks/baloo-5.88.0/work/baloo-5.88.0/src/engine/writetransaction.cpp:319
#12 0x00007fa692e46f41 in Baloo::Transaction::commit (this=0x560399116450) at
/var/tmp/portage/kde-frameworks/baloo-5.88.0/work/baloo-5.88.0/src/engine/transaction.cpp:272
#13 0x000056039817888c in Baloo::App::processNextFile (this=0x7ffe426976e0) at
/var/tmp/portage/kde-frameworks/baloo-5.88.0/work/baloo-5.88.0/src/file/extractor/app.cpp:109
#14 0x00007fa6925c10c6 in QObject::event (this=0x7ffe426976e0,
e=0x56039916de70) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qobject.cpp:1314
#15 0x00007fa692595828 in QCoreApplication::notifyInternal2
(receiver=0x7ffe426976e0, event=0x56039916de70) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qcoreapplication.cpp:1064
#16 0x00007fa692598e95 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5603990e2f80) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qcoreapplication.cpp:1821
#17 0x00007fa6925e7ea3 in postEventSourceDispatch (s=0x5603990e4650) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#18 0x00007fa69120d13b in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#19 0x00007fa69120d3f8 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fa69120d4af in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#21 0x00007fa6925e7934 in QEventDispatcherGlib::processEvents
(this=0x560399136350, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r10/work/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#22 0x00007fa69259421b in QEventLoop::exec (this=this@entry=0x7ffe42697650,
flags=..., flags@entry=...) at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/global/qflags.h:69
#23 0x00007fa69259c84d in QCoreApplication::exec () at
../../include/QtCore/../../../qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/global/qflags.h:121
#24 0x0000560398175366 in main (argc=<optimized out>, argv=0x7ffe426976e0) at
/var/tmp/portage/kde-frameworks/baloo-5.88.0/work/baloo-5.88.0/src/file/extractor/main.cpp:37
[Inferior 1 (process 17429) detached]

It crashes too when I try to clear one file using the command 'balooctl clear'.
Baloosearch works, so maybe the database itself is not broken completely this
time.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to