Bug 342673 - Rebuild fingerprints crashes with large number (>110000) of images
Summary: Rebuild fingerprints crashes with large number (>110000) of images
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Similarities (show other bugs)
Version: 4.12.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-09 21:14 UTC by Rainer Lay
Modified: 2018-09-02 16:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0


Attachments
Backtrace with digikam 4.9.0 (38.72 KB, text/plain)
2015-04-07 21:45 UTC, Rainer Lay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Lay 2015-01-09 21:14:29 UTC
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)
Comment 1 Rainer Lay 2015-01-16 17:50:01 UTC
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?
Comment 2 caulier.gilles 2015-03-25 08:50:02 UTC
Problem still reproducible with last stable digiKam 4.8.0 ?

Gilles Caulier
Comment 3 Rainer Lay 2015-03-25 19:22:16 UTC
Sorry, but as of now, I couldn't find a windows 4.8.0 version.
Comment 4 Rainer Lay 2015-03-25 22:12:54 UTC
meanwhile, 4.6.0 is available. I installed it and the error is still there.
Comment 5 Rainer Lay 2015-03-26 06:39:40 UTC
meanwhile, 4.7.0 is available. I installed it and the error is still there.
Comment 6 Rainer Lay 2015-03-27 06:35:14 UTC
meanwhile, 4.8.0 is available. I installed it and the error is still there.
Thanx for the current windows versions.
Comment 7 Rainer Lay 2015-04-07 21:44:44 UTC
meanwhile, 4.9.0 is available. I installed it and the error is still there.
Thanx for the current windows versions.
Comment 8 Rainer Lay 2015-04-07 21:45:49 UTC
Created attachment 91936 [details]
Backtrace with digikam 4.9.0
Comment 9 caulier.gilles 2015-04-08 05:03:09 UTC
Same problem than bug #339008. The crash is in PreviewWidget constructor.

*** This bug has been marked as a duplicate of bug 339008 ***
Comment 10 Rainer Lay 2015-05-13 19:20:39 UTC
meanwhile, 4.10.0 is available. I installed it and the error is still there.
Thanx for the current windows versions.
Comment 11 Rainer Lay 2015-08-07 17:27:26 UTC
This bug is still valid with version 4.12.0 on windows.
Comment 12 caulier.gilles 2018-09-02 16:50:54 UTC
Not reproducible with 6.0.0