Created attachment 122500 [details] Backtrace of the crash SUMMARY Today I had to tag a bunch of new pictures (around 800). I experienced three crashes during that process. I don't recall doing anything specific, just selecting pictures in the miniture view, using the Captions panel to tag, and switching to the map panel from time to time to check the location of a picture with GPS coordinates. The third time I started digikam in debug mode, so I could capture the error and run the backtrace. I have attached the textfile with the output of the console. In short, this is the main error message: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x00007fffe1ae5bf0 in ubrk_following () from /tmp/.mount_digikabK4AdX/usr/lib/libicuuc.so.58 This may be related to Bug 407914 and Bug 392607, but that's for you to judge. I hope it helps. Thanks! PS: I'm using digikam-6.3.0-git-20190825T034937-x86-64.appimage under Ubuntu 18.04 LTS
Form your trace, it's clear, the crash appear in Map view and the problem come from Qt5WebKit (when you move map canvas with mouse) : #0 0x00007fffe1ae5bf0 in ubrk_following () from /tmp/.mount_digikabK4AdX/usr/lib/libicuuc.so.58 #1 0x00007fffef63afdc in WebCore::findWordBoundary(WTF::StringView, int, int*, int*) () from /tmp/.mount_digikabK4AdX/usr/lib/libQt5WebKit.so.5 #2 0x00007fffef6b86d1 in WebCore::startWordBoundary(WTF::StringView, unsigned int, WebCore::BoundarySearchContextAvailability, bool&) () from /tmp/.mount_digikabK4AdX/usr/lib/libQt5WebKit.so.5 #3 0x00007fffef6e4a6e in WebCore::backwardSearchForBoundaryWithTextIterator(WebCore::SimplifiedBackwardsTextIterator&, WTF::Vector<unsigned short, 1024ul, WTF::CrashOnOverflow, 16ul>&, unsigned int, unsigned int (*)(WTF::StringView, unsigned int, WebCore::BoundarySearchContextAvailability, bool&)) () from /tmp/.mount_digikabK4AdX/usr/lib/libQt5WebKit.so.5
Today, next digiKam 7.0.0 beta2 64 bits pre-release AppImage bundle will be published with last Qt5.14 and QtWebEngine by default (instead QtWebkit). Please test and give us a feedback to see if problem remain on your computer. https://files.kde.org/digikam/ Thanks in advance Giles Caulier
Not reproducible with 7.0.0 beat2. see bug #413855 for details... Gilles Caulier
I have not experienced this bug in quite some time now. You can close it if you think it's no longer relevant.