| Summary: | Crash after changing the collection | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Paulo Fidalgo <paulo.fidalgo.pt> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 7.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/2519366789ec8767077bb845fadea2126fcde886 | Version Fixed/Implemented In: | 8.0.0 |
| Sentry Crash Report: | |||
|
Description
Paulo Fidalgo
2022-07-02 12:35:37 UTC
The QFatal exception appear. It must be generated internally by Qt. Please post the debug trace of application (not the GDB trace). digiKam is verbose and these information can help to investiguate. See the details at: https://www.digikam.org/contribute/ Gilles Caulier Another tip: please try the digiKam 7.7.0 appimage linux bundle instead the system package. https://download.kde.org/stable/digikam/7.7.0/ Gilles Caulier The cause is clear, 2 threads access a QVector List, one writes, one reads. This causes a crash. We need a mutex here. Maik Git commit 2519366789ec8767077bb845fadea2126fcde886 by Maik Qualmann. Committed on 02/07/2022 at 17:10. Pushed by mqualmann into branch 'master'. protect album child cache QVector with a QReadWriteLock If no problems occur we can it backport to digiKam-7.8.0. FIXED-IN: 8.0.0 M +2 -1 NEWS M +31 -3 core/libs/album/engine/album.cpp M +6 -3 core/libs/album/engine/album.h https://invent.kde.org/graphics/digikam/commit/2519366789ec8767077bb845fadea2126fcde886 |