| Summary: | Digikam 8.2.0 segfaults on importing collection | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | a52ca063 |
| Component: | Import-MainView | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.6.0 | |
| Sentry Crash Report: | |||
|
Description
a52ca063
2024-01-26 12:46:27 UTC
I have a coredump, but it is 1.5 GB in size. If there is a way for me to cut that down where it can still be useful, please let me know. Please create a simple GDB backtrace as described here: https://www.digikam.org/contribute/ Maik Git commit 2fcf896234e692ead19a3bb14aab8f16c2e621d3 by Maik Qualmann. Committed on 26/01/2024 at 22:36. Pushed by mqualmann into branch 'master'. switch to QMutex to protect album child cache and protect the correct parent child cache. Related: bug 480373 FIXED-IN: 8.3.0 M +1 -1 NEWS M +15 -11 core/libs/album/engine/album.cpp M +2 -2 core/libs/album/engine/album.h https://invent.kde.org/graphics/digikam/-/commit/2fcf896234e692ead19a3bb14aab8f16c2e621d3 Git commit d92bb3d84dc8634a7c5634e2626fee6f932c7e4d by Maik Qualmann. Committed on 27/01/2024 at 11:41. Pushed by mqualmann into branch 'master'. revert to QReadWriteLocker and protect the right parent child cache Related: bug 480373 M +11 -15 core/libs/album/engine/album.cpp M +2 -2 core/libs/album/engine/album.h https://invent.kde.org/graphics/digikam/-/commit/d92bb3d84dc8634a7c5634e2626fee6f932c7e4d @a52ca063, digiKam 8.3.0 stable version is released and available at usual place : https://www.digikam.org/download/ Can you reproduce the dysfunction on your computer ? Thanks in advance Gilles Caulier Hi, digiKam 8.5.0. is out with many fixes and improvements. https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/ This report still valid with this version? Thanks in advance Gilles Caulier I tested this in 8.4.0 and am no longer encountering this issue. Whatever changed between 8.2.0 and 8.4.0 resolved the issue for me. Many thanks, Walter |