NB baloo_file_extractor (not baloo_file). An example, although "The generated crash information is probably not useful": ---- Application: baloo_file_extractor (baloo_file_extractor), signal: Segmentation fault [KCrash Handler] #7 0x000000080040b9a6 in () at /usr/local/lib/liblmdb.so.0 #8 0x000000080040590c in mdb_cursor_put () at /usr/local/lib/liblmdb.so.0 #9 0x000000080040d98c in mdb_put () at /usr/local/lib/liblmdb.so.0 #10 0x00000008003cc1e4 in Baloo::PositionDB::put(QByteArray const&, QVector<Baloo::PositionInfo> const&) () at /usr/local/lib/libKF5BalooEngine.so.5 #11 0x00000008003dc694 in Baloo::WriteTransaction::commit() () at /usr/local/lib/libKF5BalooEngine.so.5 #12 0x00000008003d4ad3 in Baloo::Transaction::commit() () at /usr/local/lib/libKF5BalooEngine.so.5 #13 0x000000000020ea91 in () #14 0x0000000801074a11 in () at /usr/local/lib/qt5/libQt5Core.so.5 #15 0x0000000801062d3c in QObject::event(QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #16 0x00000008010385bd in QCoreApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #17 0x00000008010381bd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #18 0x000000080108f94a in QTimerInfoList::activateTimers() () at /usr/local/lib/qt5/libQt5Core.so.5 #19 0x000000080109139d in () at /usr/local/lib/qt5/libQt5Core.so.5 #20 0x00000008029ea12e in g_main_context_dispatch () at /usr/local/lib/libglib-2.0.so.0 #21 0x00000008029ea4d4 in () at /usr/local/lib/libglib-2.0.so.0 #22 0x00000008029ea596 in g_main_context_iteration () at /usr/local/lib/libglib-2.0.so.0 #23 0x0000000801090a60 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/local/lib/qt5/libQt5Core.so.5 #24 0x0000000801034757 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/local/lib/qt5/libQt5Core.so.5 #25 0x000000080103885e in QCoreApplication::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #26 0x000000000020e3ca in () #27 0x000000000020ca20 in () #28 0x000000000020c920 in () #29 0x0000000000000000 in () [Inferior 1 (process 5305) detached] ---- % date ; uname -KUv Sat 17 Jul 2021 09:28:31 BST FreeBSD 14.0-CURRENT #100 main-n247798-f39dd6a9784: Thu Jul 8 07:38:23 BST 2021 root@mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 1400025 1400025 % pkg info -x baloo baloo-widgets-21.04.3 kf5-baloo-5.83.0 % ls -hlrt baloo*.core -rw------- 1 grahamperrin grahamperrin 256G 15 Jul 23:50 baloo_file.core -rw------- 1 grahamperrin grahamperrin 41M 16 Jul 02:03 baloo_file_extracto.core % uptime 9:32a.m. up 1:44, 6 users, load averages: 0.48, 0.80, 1.07 % ---- I understand, from discussion in IRC, that Baloo is "… complicated and has a lot of different layers. …", so I don't expect fixes for bugs such as this to be easy or quick.
### Background to this morning's crash of baloo_file_extractor The screenshot at <https://bz-attachments.freebsd.org/attachment.cgi?id=226502> preceded a restart of the OS (and is borrowed from bug 257226). htop, filtered to show: baloo Four of four CPUs were hogged, by kernel (PID 0) if I recall correctly. I suspected that baloo_file_extractor was the underlying cause. Not long after killing this process, hogging of the CPUs ceased. ### Side note Bug 234830 (closed, fixed) catches my eye: > … baloo_file_extractor hangs at tiff file, consuming 100% cpu I should, ideally, positively identify the cause of hogging in my case, but this will be a bug for another day.
Created attachment 226503 [details] Screenshot: apparently indexing, 18% complete, idle ### Background (continued) This screenshot was taken after restarting the OS _and_ killing the lower numbered of two baloo_file processes (see bug 257226). htop, filtered to show: baloo If I recall correctly, the shot was preceded by: * a tree of two baloo_file_extractor processes – under the higher numbered baloo_file process. I waited a while, did not observe reappearance of a baloo_file_extractor process. The 'Pause Indexer' button can be clicked, and darkens whilst clicked, however there's no change to the status; it remains _reportedly_: > Indexing file content, 18% complete > > Currently indexing: Idle
(In reply to Graham Perrin from comment #2) > … This screenshot was taken after restarting the OS _and_ killing the lower numbered of two baloo_file processes … A possible correction (sorry), I'm no longer certain that a baloo_file killing had been performed. This shot might have been taken during my _first_ Plasma session following the restart of the OS.
Created attachment 226504 [details] Screenshot: KDE Crash Handler dialogue, 08:15 this morning ### Background (continued) Foreground: KDE Crash Handler dialogue. Mid ground: System Settings, no progress beyond the 18% completion that was measured around ten minutes earlier. Rear ground: htop, two baloo_file processes, the lower numbered of which (4647) was seen in the screenshot at comment 2. The crashing baloo_file_extractor is under the higher numbered baloo_file process (5071). ---- % date ; uptime Sat 17 Jul 2021 10:02:02 BST 10:02a.m. up 2:13, 6 users, load averages: 0.40, 0.66, 0.81 % grep baloo /var/log/messages Jul 12 10:15:59 mowa219-gjp4-8570p pkg[2528]: kf5-baloo upgraded: 5.82.0 -> 5.83.0 Jul 12 10:17:59 mowa219-gjp4-8570p pkg[2528]: baloo-widgets upgraded: 21.04.2 -> 21.04.3 Jul 15 23:50:16 mowa219-gjp4-8570p kernel: pid 3936 (baloo_file), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:57 mowa219-gjp4-8570p kernel: pid 42660 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:57 mowa219-gjp4-8570p kernel: pid 42661 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:57 mowa219-gjp4-8570p kernel: pid 42662 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:58 mowa219-gjp4-8570p kernel: pid 42666 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:58 mowa219-gjp4-8570p kernel: pid 42678 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:59 mowa219-gjp4-8570p kernel: pid 42681 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) Jul 16 02:03:59 mowa219-gjp4-8570p kernel: pid 42682 (baloo_file_extracto), jid 0, uid 1002: exited on signal 6 (core dumped) %
Three points: 1. as far as I can tell, no-one else in Bugzilla mentioned this report 2. off-topic, I use Recoll <https://www.freshports.org/deskutils/recoll/>, the package for which is capable of real-time indexing since 37991a7381a067c2e744e7debafcf18aef664e35 <https://github.com/freebsd/freebsd-ports/commit/37991a7381a067c2e744e7debafcf18aef664e35> – I no longer attempt use of Baloo 3. no feedback. It seems reasonable for me to close this report, which I opened. If anyone finds a matching report upstream, we might reopen here. Thanks. <https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Baloo&component=Baloo+File+Daemon&component=balooctl&list_id=2185115&order=Bug+Number&query_format=advanced>