Summary: | baloo_file crashes in Baloo::IdFilenameDB::get() | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Geert Janssens <info> |
Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bob, greg.sheppard, nate, wbauer1 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.36.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Geert Janssens
2017-10-17 08:15:48 UTC
Git commit f57c4bc27b81f2b40d910d376a0bb531cd8472c6 by Stefan Brüns. Committed on 03/05/2018 at 22:37. Pushed by bruns into branch 'master'. Avoid infinite loops when fetching the URL from DocumentUrlDB Summary: Some users apparently have DBs which contain infinite loops in the idTree (a parentId pointing to itself or one of its children). This manifests in either crashes due to exhausted memory and/or the process being stuck with 100% CPU load. The problem can only be completely solved by either recreating the DB, or by cleaning the DB from any problematic records. As in interim solution, stop the code from crashing. Related: bug 378754, bug 391258, bug 393181 Reviewers: #baloo, michaelh, #frameworks, ngraham Reviewed By: ngraham Subscribers: ngraham, #frameworks Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D12335 M +10 -2 src/engine/documenturldb.cpp https://commits.kde.org/baloo/f57c4bc27b81f2b40d910d376a0bb531cd8472c6 How can I clean the db ? I have searched for this but didn't find an obvious answer. (In reply to Geert Janssens from comment #2) > How can I clean the db ? I have searched for this but didn't find an obvious > answer. Delete or rename ~/.local/share/baloo/. Everything has to be reindexed afterwards of course. Created attachment 114344 [details]
New crash information added by DrKonqi
baloo_file_extractor (5.47.0) using Qt 5.9.6
- What I was doing when the application crashed: logged into plasma after a fresh boot, crash appeared instantly. Happens nearly every login, except one time very recently Baloo did not crash but gradually consumed all memory. That time, I rebooted, and it crashed on first login as usual.
-- Backtrace (Reduced):
#6 0x00007fece6ca248b in Baloo::IdFilenameDB::get(unsigned long long) () from /lib64/libKF5BalooEngine.so.5
#7 0x00007fece6c9bdaf in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5
#8 0x00007fece6cac7c4 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5
#9 0x00005591e2ab1bd8 in Baloo::App::processNextFile() ()
#10 0x00007fece4bc9a24 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5
*** Bug 393756 has been marked as a duplicate of this bug. *** *** Bug 393896 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 372880 *** |