Summary: | baloo_file crashes in Baloo::IdFilenameDB::get() | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Solerman Kaplon <solerman> |
Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aime.sournies, greg.sheppard, hacker, info, kde, kdebugs, mengchao0532, missakiiki, nate, necker, reinhardauner |
Priority: | HI | Keywords: | drkonqi |
Version: | 5.18.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=434926 | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Solerman Kaplon
2016-11-24 10:58:41 UTC
*** Bug 385846 has been marked as a duplicate of this bug. *** *** Bug 393756 has been marked as a duplicate of this bug. *** *** Bug 393896 has been marked as a duplicate of this bug. *** *** Bug 375190 has been marked as a duplicate of this bug. *** *** Bug 380028 has been marked as a duplicate of this bug. *** *** Bug 403620 has been marked as a duplicate of this bug. *** *** Bug 405084 has been marked as a duplicate of this bug. *** *** Bug 405170 has been marked as a duplicate of this bug. *** Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 395888, bug 367480, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9 src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0 -1 src/engine/documenturldb.cpp M +4 -3 src/engine/documenturldb.h M +4 -5 src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0 -2 src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4 -4 src/engine/transaction.h M +3 -2 src/file/extractorprocess.cpp M +5 -5 src/file/fileindexscheduler.cpp M +5 -4 src/file/indexcleaner.cpp M +0 -1 src/file/main.cpp M +1 -1 src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d *** Bug 406064 has been marked as a duplicate of this bug. *** Created attachment 119213 [details]
New crash information added by DrKonqi
baloo_file (5.55.0) using Qt 5.9.7
- What I was doing when the application crashed:
I had open Google Chrome and was surfing the internet - additionally, amarok was running.
-- Backtrace (Reduced):
#6 Baloo::IdFilenameDB::get (this=this@entry=0x7f33d3bcb9f0, docId=<optimized out>, docId@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/idfilenamedb.cpp:96
#7 0x00007f73de612d1f in Baloo::DocumentUrlDB::get (this=this@entry=0x7f33d3bcba70, docId=docId@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/documenturldb.cpp:134
#8 0x00007f73de623734 in Baloo::Transaction::documentUrl (this=this@entry=0x7f33d3bcbb20, id=id@entry=11059540789267) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/engine/transaction.cpp:104
#9 0x000055baa424071e in Baloo::UnindexedFileIndexer::run (this=0x55baa696fec0) at /usr/src/debug/baloo5-5.55.0-lp151.2.2.x86_64/src/file/unindexedfileindexer.cpp:62
#10 0x00007f73dda6fe22 in QThreadPoolThread::run (this=0x55baa6977100) at thread/qthreadpool.cpp:99
*** Bug 406317 has been marked as a duplicate of this bug. *** *** Bug 406378 has been marked as a duplicate of this bug. *** Four days ago, I rebooted my Tumbleweed system after some software upgrades and got no warning pop-up messages. The baloo_file_extractor is finally doing something. For all the four days, it, and 14 tags.so processes have been using 98-100% of each of the 12 CPU cores continuously. They do not appear to be impeding other processes so no worries on that score. I'll just leave things alone and assume they'll be finished whatever it is they're doing one of these days. *** Bug 410097 has been marked as a duplicate of this bug. *** *** Bug 411842 has been marked as a duplicate of this bug. *** *** Bug 416197 has been marked as a duplicate of this bug. *** No duplicate report is newer than Frameworks 5.55, which is almost two years old. After all the bugfixing work done during that time, I think we can call this fixed! |