[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #10 from Maik Qualmann --- Git commit 7c7a6406839ed9c233d14bf935b642cb96af6425 by Maik Qualmann. Committed on 27/10/2023 at 22:23. Pushed by mqualmann into branch 'master'. fix race condition with uninitialized similarity database Related:

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #8 from Ian Darwin --- Please close; as I mentioned I can no longer reproduce the problem. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #7 from caulier.gil...@gmail.com --- Ian, Please review the last comment from me and Maik about this entry. We needs a fresh feedback, else we will close the file as well... Best regards Gilles Caulier -- You are receiving this mail beca

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #6 from caulier.gil...@gmail.com --- Ian, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance Gilles Caulier -- You are receiving this mail because: You are wa

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla: https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/ Can you reproduce the dysfunction with this

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #4 from Maik Qualmann --- As I said, the crash can no longer be reproduced exactly. the QApplication ist crashed and exits, the databases were cleaned up, but the ScanController thread did not stop. It can also hit the core database. We woul

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #3 from Ian Darwin --- Thank you!!! I feel like a goof. Moving all the .db files out of ~/Pictures lets it start up, and it's busy doing what I presume is making tens of thousands of thumbnails in the background. If you think it is worthw

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Similarity C

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 --- Comment #2 from Maik Qualmann --- This problem can only occur if the similarity database has not been initialized. Which cannot actually not occur because the pointer is always assigned a value. I suspect there was a crash while scanning and parts o

[digikam] [Bug 430858] Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105

https://bugs.kde.org/show_bug.cgi?id=430858 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik