digikam was compiled from git master on 5/21 (today). Splash screen says 4.1.0 Reproducible: Didn't try Steps to Reproduce: 1. tools->maint.->update metadata image to database 2. Do nothing while waiting for the crash 3. Actual Results: Crash Expected Results: database should have image metadata in it.
Created attachment 86760 [details] digikam log output from gdb. log from running digikam in gdb.
I'm not sure if crash appear in DB. The gdb backtrace is uncomplete. you pass from thread 100 to 6. It miss data. Sound like backtrace is corrupted. Re-run digiKam in GDB as explained here to get a better backtrace : http://www.digikam.org/contrib
Created attachment 86762 [details] New debug backtrace output
Created attachment 86764 [details] Yet another backtrace - with debuginfo included digikam crashes very quickly. This is highly repeatable.
It crash in Exiv2 shared lib, not digiKam as well, probably when image are scanned at startup. (gdb) #0 0x00000035ec05f0e1 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #1 0x00000033e6ee54a6 in Exiv2::ImageFactory::open(std::string const&) () from /usr/lib64/libexiv2.so.13 #2 0x00007ffff75e356a in KExiv2Iface::KExiv2::load (this=0x7fff800564a0, filePath=...) at /home/shipman/Downloads/dk/extra/libkexiv2/libkexiv2/kexiv2.cpp:298 #3 0x00007ffff6e54cf9 in Digikam::DMetadata::load (this=0x7fff800564a0, filePath=...) Please report this problem to Exiv2 project, and try to identify which image crash exiv2 to join file on your report Best Gilles Caulier
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4