Bug 471206

Summary:	Baloo File Extractor Crashes on login
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	tomwilliams34
Component:	Baloo File Daemon	Assignee:	baloo-bugs-null
Status:	RESOLVED FIXED
Severity:	crash	CC:	stefan.bruens, tagwerk19
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.107.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	5.108.0
Sentry Crash Report:

Description tomwilliams34 2023-06-18 22:03:46 UTC

Application: baloo_file_extractor (5.107.0)

Qt Version: 5.15.9
Frameworks Version: 5.107.0
Operating System: Linux 6.3.8-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Crash appears on login, no clear change in behaviour to user experience after this (though I did not regularaly use the baloo file indexer to full potential). This crash appears after a recent update.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fe2b9b7d1b7 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#5  0x00007fe2b9fb16ad in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0
#6  0x00007fe2b9fb180e in mdb_put () from /lib64/liblmdb.so.0.0.0
#7  0x00007fe2baf2a520 in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /lib64/libKF5BalooEngine.so.5
#8  0x00007fe2baf38d51 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5
#9  0x00007fe2baf2d4f1 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5
#10 0x00005632feeed18c in Baloo::App::processNextFile() ()
#11 0x00007fe2ba2ebc6a in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007fe2ba2df6bb in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007fe2ba2b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007fe2ba305c6b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#15 0x00007fe2ba3065a1 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#16 0x00007fe2b911339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007fe2b9171438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#18 0x00007fe2b9110a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007fe2ba306919 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007fe2ba2b270b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007fe2ba2ba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x00005632feee305b in main ()
[Inferior 1 (process 2233) detached]

The reporter indicates this bug may be a duplicate of or related to bug 420296, bug 420615, bug 420677, bug 422393, bug 428123, bug 450988, bug 465529, bug 467485.

Reported using DrKonqi

Comment 1 Stefan Brüns 2023-11-13 08:08:54 UTC

(Untested) Memory constraints interfering with regular operation, fixed.

Comment 2 tagwerk19 2023-11-14 17:15:42 UTC

It would be interesting to know what
    systemctl --user status kde-baloo
says...

In particular the line giving details of "Memory" (it should mention "High" and "Max" limits and Swap "Max")

You might however find that updating Fedora (so you are at Frameworks 5.110), purging and reindexing, perhaps with a bit of patience, gets you back on the level. See:
    https://discuss.kde.org/t/baloo-and-frameworks-5-111/6348
Fedora "cherry picked" the patch so you don't need 5.111