| Summary: | Crash with segmentation fault when writing a large amount of metadata to images | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | dippon |
| Component: | Maintenance-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.2.0 | |
| Sentry Crash Report: | |||
|
Description
dippon
2018-11-11 17:16:49 UTC
Hi, I'm working on this issue since one week, by deploying unit tests around internal digiKam Exiv2 interface. My investigations indicate a non re-entrancy with all Exiv2 API. As all is multithreaded in digiKam, you can imagine the side effect. So, with current implementation from git/master (next 6.0.0 release), i protected all Exiv2 API calls with mutex to prevent crash. This have really improved the stability tested by unit test as expected, but this introduce time latency everywhere. So the database to image metadata synchronization will slow down, but typically more stable. Also, with the bundles that we provided, we use now the Exiv2 0.27 RC1, not yet released, but coming with plenty of bug fixes. So, i recommend to make a try with DK 6.0.0-beta3 appimage linux bundle, just build today and available here : https://files.kde.org/digikam/ Take a care : with 6.0.0, the database schema has changed, compared to 5.9.0. Running 6.0.0 in place will upgrade the database, you cannot re-use it later with 5.9.0. I recommend to make a test collection to verify the improvements. Do not use yet in production as well... Best Gilles Caulier Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ Good news, After 2 weeks of works, the pre-release 6.1.0 bundles are now reconstructed from scratch with: - All OpenCV options for CUDA, OPenMP, and OPenCL disabled to prevent crashes in face management. - A large upgrade of Qt5 from 5.9.7 to 5.11.3. - An upgrade to KF5 5.55. - An upgrade to Ffmpeg 3.3.9 - The fontconfig/freetype integration in the bundle to reduce system dependencies Files can be downloaded here : https://files.kde.org/digikam/ Please test and report. Gilles Caulier Hi, Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier This problem has been fixed in digiKam-7.2.0. We are now waiting until the thumbnail threads are finished and returns. I close the bug. Maik |