| Summary: | Digikam 7.1.0 crash Assert d in similaritydbaccess.cpp line 105 | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Ian Darwin <ian> |
| Component: | Database-Similarity | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | OpenBSD | ||
| OS: | OpenBSD | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
| Attachments: | Digikam stack trace for Assert fail in similaritydbaccess.cpp | ||
|
Description
Ian Darwin
2020-12-27 15:14:23 UTC
Did you update a very old digiKam database? Because an update from V4 to V7 was carried out. An error may have occurred while creating the similarity database. Activate the debug output and give us the log from the terminal as described here: https://www.digikam.org/contribute/ Maik 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 of digiKam were already in delete mode. The scanner thread then encountered zo the pointer that had already been deleted. So we need a better backtrace, don't forget "bt" next time. Maik 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 worthwhile, I can try to switch the new db files out for the old and give you debug log and bt. Thanks Ian On 12/27/20 10:26 AM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=430858 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> --- > Did you update a very old digiKam database? Because an update from V4 to V7 was > carried out. An error may have occurred while creating the similarity database. > Activate the debug output and give us the log from the terminal as described > here: https://www.digikam.org/contribute/ > > Maik > 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 would have to use the debug output to determine which file was last scanned and triggered the crash. Maik 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 version ? Thanks in advance for your feedback Gilles Caulier Ian, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance Gilles Caulier 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 Please close; as I mentioned I can no longer reproduce the problem. not reproducible with 7.5.0. Closed 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: bug 476157 FIXED-IN: 8.2.0 M +1 -1 NEWS M +5 -5 core/libs/album/manager/albummanager_database.cpp M +2 -2 core/libs/database/utils/scan/scancontroller.cpp M +9 -0 core/libs/database/utils/scan/scancontroller.h M +11 -0 core/libs/database/utils/scan/scancontroller_start.cpp https://invent.kde.org/graphics/digikam/-/commit/7c7a6406839ed9c233d14bf935b642cb96af6425 |