When trying to create finger prints, digikam crashes. Reproducible: Always Steps to Reproduce: 1.Start digiKam 2.Select folder with large number of pictures, 3.Select Tools -> Maintenance -> Rebuild Fingerprints 4.Wait for it to fail. Actual Results: Get crash window Expected Results: Finished fingerprinting all images and allowed me to add tags as needed. Some backtraces: ------------------------------------------------------------------------------------------------------------- -- multi core [New Thread 1308.0x1500] [New Thread 1308.0x1954] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1308.0x1640] 0x031137b0 in digikamlib!?metaObject@SharpSettings@Digikam@@UBEPBUQMetaObject@@XZ () from C:\Program Files (x86)\digiKam\bin\digikamlib.dll (gdb) bt #0 0x031137b0 in digikamlib!?metaObject@SharpSettings@Digikam@@UBEPBUQMetaObject@@XZ () from C:\Program Files (x86)\digiKam\bin\digikamlib.dll #1 0x3bb67641 in ?? () #2 0x07e10150 in ?? () #3 0xba000000 in ?? () #4 0x00000bc0 in ?? () #5 0x000007d0 in ?? () #6 0x7cab0020 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) ------------------------------------------------------------------------------------------------------------- -- single core warning: QThread::start: Failed to create thread (Der Zugriffscode ist unzul?ssig.) gdb: unknown target exception 0xe06d7363 at 0x7704c42d Program received signal ?, Unknown signal. [Switching to Thread 6476.0x1bac] 0x7704c42d in RaiseException () from C:\Windows\syswow64\KernelBase.dll (gdb) bt #0 0x7704c42d in RaiseException () from C:\Windows\syswow64\KernelBase.dll #1 0x7851872d in MSVCR100!_CxxThrowException () from C:\Program Files (x86)\digiKam\bin\msvcr100.dll #2 0x6621a283 in QtCore4!?qBadAlloc@@YAXXZ () from C:\Program Files (x86)\digiKam\bin\QtCore4.dll (gdb) ------------------------------------------------------------------------------------------------------------- -- single core -- 600MB memory, 3,6 GB free -- 18795 finger prints processed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 6572.0x1b1c] 0x514637b0 in digikamlib!?metaObject@SharpSettings@Digikam@@UBEPBUQMetaObject@@XZ () from C:\Program Files (x86)\digiKam\bin\digikamlib.dll (gdb) bt #0 0x514637b0 in digikamlib!?metaObject@SharpSettings@Digikam@@UBEPBUQMetaObject@@XZ () from C:\Program Files (x86)\digiKam\bin\digikamlib.dll #1 0x4659d7f1 in ?? () #2 0x79a38070 in ?? () #3 0xba000000 in ?? () #4 0x00000bc0 in ?? () #5 0x000007d0 in ?? () #6 0x7caf0020 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb)
I tried to get a backtrace with windbg to, but it complains about missing symbols. Is there a way to get the symbols like described for Libreoffice in https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg?
Problem still reproducible with last stable digiKam 4.8.0 ? Gilles Caulier
Sorry, but as of now, I couldn't find a windows 4.8.0 version.
meanwhile, 4.6.0 is available. I installed it and the error is still there.
meanwhile, 4.7.0 is available. I installed it and the error is still there.
meanwhile, 4.8.0 is available. I installed it and the error is still there. Thanx for the current windows versions.
meanwhile, 4.9.0 is available. I installed it and the error is still there. Thanx for the current windows versions.
Created attachment 91936 [details] Backtrace with digikam 4.9.0
Same problem than bug #339008. The crash is in PreviewWidget constructor. *** This bug has been marked as a duplicate of bug 339008 ***
meanwhile, 4.10.0 is available. I installed it and the error is still there. Thanx for the current windows versions.
This bug is still valid with version 4.12.0 on windows.
Not reproducible with 6.0.0