Summary: | Baloo File Extractor crashes on system startup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | James Clarke <james> |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | abrahao_rj, christoph, m0rgi0n999, serge.delfaut, tagwerk19 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.115.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
James Clarke
2024-02-21 08:27:53 UTC
(In reply to James Clarke from comment #0) > ... > #10 0x00007874cc5ee991 in mdb_assert_fail.constprop.0 (env=0x5c87117b4640, expr_txt=<optimized out>, func=<optimized out>, line=<optimized out>, file=0x7874cc5fb7f1 "mdb.c") at /usr/src/debug/lmdb/openldap/libraries/liblmdb/mdb.c:1588 > ... > #19 0x00007874cd5597f7 in Baloo::DocumentDB::del (this=<optimized out>, docId=<optimized out>) at /usr/src/debug/baloo5/baloo-5.115.0/src/engine/documentdb.cpp:103 > #20 0x00007874cd56fcb8 in Baloo::WriteTransaction::removeDocument (this=0x5c87117ee430, id=94741231883520018) at /usr/src/debug/baloo5/baloo-5.115.0/src/engine/writetransaction.cpp:129 > ... Seems that "clean up" after deleting file is particularly fragile, there seems to be a fair number of crashes happening after a "removeDocument". Not all crashes, certainly, but many... There's a suspicion here: https://bugs.kde.org/show_bug.cgi?id=389848#c178 > In the middle of txn 0x5638e7e58130 the init sequence occurs again, and all of the > contents of this logfile are only being written by a single process. That means baloo_file > has opened the same env twice in the same process, which is explicitly forbidden by the > LMDB docs. http://www.lmdb.tech/doc/ Maybe the issue can be pinned down to the delete code... (In reply to tagwerk19 from comment #1) > ... there seems to be a fair number of crashes happening after a "removeDocument". Not > all crashes, certainly, but many... See: Bug 405284 Bug 467769 Bug 472197 Bug 472540 Bug 481429 We always delete the lock file, until that is fixed, all hope is lost, see the linked bug. *** This bug has been marked as a duplicate of bug 389848 *** *** Bug 485071 has been marked as a duplicate of this bug. *** |