Bug 470443 - Baloo crash indexing
Summary: Baloo crash indexing
Status: RESOLVED FIXED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.106.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-05-30 08:53 UTC by Alessandro Nigris
Modified: 2023-06-06 10:03 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 Alessandro Nigris 2023-05-30 08:53:59 UTC
Application: baloo_file_extractor (5.106.0)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.2.10-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
On Tumbleweed baloo_file_extractor crashes during indexing of files. On resume Baloo seems to work, but monitor shows nothing. So ordinary search in folders does not work (notihing found). Need to use kfind, to find anything.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Estrattore di file Baloo (baloo_file_extractor), signal: Aborted

[KCrash Handler]
#4  0x00007ffa3649490c in __pthread_kill_implementation () from /lib64/libc.so.6
#5  0x00007ffa36443196 in raise () from /lib64/libc.so.6
#6  0x00007ffa3642b897 in abort () from /lib64/libc.so.6
#7  0x00007ffa36921d4d in ?? () from /lib64/liblmdb-0.9.30.so
#8  0x00007ffa36920158 in ?? () from /lib64/liblmdb-0.9.30.so
#9  0x00007ffa3692d8d6 in ?? () from /lib64/liblmdb-0.9.30.so
#10 0x00007ffa36925103 in ?? () from /lib64/liblmdb-0.9.30.so
#11 0x00007ffa36926d2c in ?? () from /lib64/liblmdb-0.9.30.so
#12 0x00007ffa36929816 in mdb_cursor_put () from /lib64/liblmdb-0.9.30.so
#13 0x00007ffa3692a757 in mdb_put () from /lib64/liblmdb-0.9.30.so
#14 0x00007ffa379e627d in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /lib64/libKF5BalooEngine.so.5
#15 0x00007ffa379f42f7 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5
#16 0x00007ffa379e9099 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5
#17 0x0000563be4a08fdc in ?? ()
#18 0x00007ffa36d290a2 in ?? () from /lib64/libQt5Core.so.5
#19 0x00007ffa36d18b5b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#20 0x00007ffa36cec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#21 0x00007ffa36d45319 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#22 0x00007ffa36d45bfc in ?? () from /lib64/libQt5Core.so.5
#23 0x00007ffa357168d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#24 0x00007ffa35716ce8 in ?? () from /lib64/libglib-2.0.so.0
#25 0x00007ffa35716d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#26 0x00007ffa36d45f26 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#27 0x00007ffa36ceb40b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#28 0x00007ffa36cf38a0 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#29 0x0000563be49fee23 in ?? ()
#30 0x00007ffa3642cbb0 in __libc_start_call_main () from /lib64/libc.so.6
#31 0x00007ffa3642cc79 in __libc_start_main_impl () from /lib64/libc.so.6
#32 0x0000563be49fef45 in ?? ()
[Inferior 1 (process 7360) detached]

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

Reported using DrKonqi
Comment 1 Ben Bonacci 2023-05-31 09:51:29 UTC
*** This bug has been marked as a duplicate of bug 470088 ***
Comment 2 tagwerk19 2023-06-03 23:10:33 UTC
> ... On resume Baloo seems to work, but monitor shows nothing ...
Have a look at Bug 470382

There's been a recent change that limits the memory that baloo can use to 512 Mbyte, this issue sounds similar. You would need to edit the systemd service file for kde-baloo, following the description.
Comment 3 Alessandro Nigris 2023-06-06 10:03:48 UTC
Thank you, but solved deleting database and list of scanned folders, re-adding list of folders and recreating database. Then all works!