Created attachment 122661 [details] Backtrace of the crash SUMMARY Today digikam crashed twice while scanning for new pictures in the collection. The second time I was able to run it in debug mode and capture the backtrace. I have attached the console output to this bug report. I hope it is useful. I am using digikam-6.4.0-git-20190911T052139-x86-64.appimage under Ubuntu 18.04.
You trying 6.4.0, not 6.3.0 as annoted in this bug report. Can you check really with 6.3.0 appimage to see if problem is reproducible ? Gilles Caulier
The problem is clear, I can fix it. An SQL query is aborted because of too long a wait and the QList is then empty. The main problem is that 8 core is used and it takes more than 500ms to scan one item. Therefore the database runs into timeout. My suggestions would be MySQL or we might limit to 2 cores on SQLite. Maik
Git commit 91af8f402e9c63c6096e431fd7fa3cfb23912ad3 by Maik Qualmann. Committed on 15/09/2019 at 05:44. Pushed by mqualmann into branch 'master'. check the return value of the SQL query FIXED-IN: 6.4.0 M +2 -1 NEWS M +16 -10 core/libs/database/coredb/coredb.cpp M +2 -1 core/libs/database/coredb/coredb.h https://invent.kde.org/kde/digikam/commit/91af8f402e9c63c6096e431fd7fa3cfb23912ad3
Git commit 0ca8479b9b9ff100c30e6a7f98c17c59befe7372 by Maik Qualmann. Committed on 15/09/2019 at 06:06. Pushed by mqualmann into branch 'master'. this function has a low priority, check if there is a running transaction M +5 -0 core/libs/database/coredb/coredb.cpp M +1 -1 core/libs/database/coredb/coredb.h https://invent.kde.org/kde/digikam/commit/0ca8479b9b9ff100c30e6a7f98c17c59befe7372
Git commit e6e76cf0cf8b34f028511958070f98f457eef81a by Maik Qualmann. Committed on 15/09/2019 at 06:47. Pushed by mqualmann into branch 'master'. less locked database during the initial scan Related: bug 389652, bug 389949 FIXED-IN: 6.4.0 M +3 -1 NEWS M +8 -4 core/libs/database/collection/collectionscanner_scan.cpp https://invent.kde.org/kde/digikam/commit/e6e76cf0cf8b34f028511958070f98f457eef81a
Glad you could fix it. Gilles, sadly, the following time I started digikam, it finished the initial scan successfully (it continued where it left it), so I could not reproduce it anymore. I would need to wait until another batch of new pictures are added to the library and digikam scans them. In any case, I'll keep an eye in case it happens again and report back if necessary.
*** Bug 412453 has been marked as a duplicate of this bug. ***
*** Bug 412950 has been marked as a duplicate of this bug. ***
*** Bug 413464 has been marked as a duplicate of this bug. ***
*** Bug 413508 has been marked as a duplicate of this bug. ***
*** Bug 413944 has been marked as a duplicate of this bug. ***
*** Bug 414186 has been marked as a duplicate of this bug. ***
*** Bug 416560 has been marked as a duplicate of this bug. ***