https://bugs.kde.org/show_bug.cgi?id=400941
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com
Component|general |Maintenance-Engine
--- Comment #1 from caulier.gil...@gmail.com ---
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
--
You are receiving this mail because:
You are watching all bug changes.
