Bug 415046 - Facial Recognition crash during scan
Summary: Facial Recognition crash during scan
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Recognition (show other bugs)
Version: 6.4.0
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-11 11:23 UTC by r4c3
Modified: 2020-08-10 10:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0


Attachments
LOGFILE DIGIKAM (112.75 KB, text/plain)
2019-12-11 21:26 UTC, r4c3
Details

Note You need to log in before you can comment on or make changes to this bug.
Description r4c3 2019-12-11 11:23:58 UTC
SUMMARY
 Database Scanning Search and Recognice Faces, Software crashes and close the application without Reporting.


STEPS TO REPRODUCE
1. Face recognition Scan 17 Albums with "deep algorythm" (with one core and multiple core the same problem) during the scan the Program closes and no Report anything.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 4.19.85-1-MANJARO
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 7,7 GiB


ADDITIONAL INFORMATION

Is there a Logfile that I can attach to the BUGREPORT?
Comment 1 Maik Qualmann 2019-12-11 12:02:41 UTC
Please create a GDB backtrace as described here:

https://www.digikam.org/contribute/

Maik
Comment 2 r4c3 2019-12-11 21:26:14 UTC
Created attachment 124440 [details]
LOGFILE DIGIKAM

I have tryed to start DigiKam with gdb.
After I started Facerecognition the Programm freezes with the following report.
(see also in the attachment)

Thread 38 "Thread (pooled)" hit Catchpoint 1 (exception thrown), 0x00007ffff5038752 in __cxa_throw () from /usr/lib/libstdc++.so.6
Comment 3 Maik Qualmann 2019-12-11 21:42:41 UTC
Before you enter "quit" after the crash, you have to enter "bt" to get the backtrace.

Maik
Comment 4 r4c3 2019-12-12 05:57:31 UTC
Thank you for your help.

Here the Log at 54% Scanning stopped and the Digikam application freezes.



digikam.dimg: "/run/media/martin/sda1/Bilder/2014/2014_10_11 Mercedes spässchen Reiner/20141011_193254.jpg" : "JPEG" file identified
digikam.general: Check for finish:  51 packages, 0 infos to filter, hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter, hasFinished() false
digikam.general: Try to get preview from "/run/media/martin/sda1/Bilder/2014/2014_10_11 Mercedes spässchen Reiner/20141011_193304.jpg"
digikam.general: Preview quality:  1
digikam.dimg: "/run/media/martin/sda1/Bilder/2014/2014_10_11 Mercedes spässchen Reiner/20141011_193304.jpg" : "JPEG" file identified
digikam.general: Check for finish:  51 packages, 0 infos to filter, hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter, hasFinished() false
digikam.facesengine: detectMultiScale gave (QRect(656,10 51x51))
digikam.facesengine: Verifying face QRect(656,10 51x51) using cascade 0
digikam.facesengine: detectMultiScale: image size ( 131 , 131 ) searchIncrement 1.1 grouping 3 flags 0 min size ( 31 , 31 )
digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC profile.

Thread 691 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff1d238700 (LWP 5103)]
0x00007ffff760d58a in QMapNode<QString, QVariant>::copy(QMapData<QString, QVariant>*) const () from /usr/lib/libdigikamcore.so.6.4.0
(gdb) bt
#0  0x00007ffff760d58a in QMapNode<QString, QVariant>::copy(QMapData<QString, QVariant>*) const () at /usr/lib/libdigikamcore.so.6.4.0
#1  0x00007ffff7791aa0 in QMap<QString, QVariant>::detach_helper() () at /usr/lib/libdigikamcore.so.6.4.0
#2  0x00007ffff778fa4d in Digikam::DImg::setAttribute(QString const&, QVariant const&) () at /usr/lib/libdigikamcore.so.6.4.0
#3  0x00007ffff761dbfc in Digikam::DImgLoader::uniqueHashV2(QString const&, Digikam::DImg const*) () at /usr/lib/libdigikamcore.so.6.4.0
#4  0x00007ffff761deb7 in Digikam::DImgLoader::createHistoryImageId(QString const&, Digikam::DImg const&, Digikam::DMetadata const&) ()
    at /usr/lib/libdigikamcore.so.6.4.0
#5  0x00007ffff761e3c3 in Digikam::DImgLoader::readMetadata(QString const&) () at /usr/lib/libdigikamcore.so.6.4.0
#6  0x00007fffc81ad21b in DigikamJPEGDImgPlugin::DImgJPEGLoader::load(QString const&, Digikam::DImgLoaderObserver*) ()
    at /usr/lib/qt/plugins/digikam/dimg/DImg_JPEG_Plugin.so
#7  0x00007ffff77854c3 in Digikam::DImg::load(QString const&, int, Digikam::DImgLoaderObserver*, Digikam::DRawDecoding const&) ()
    at /usr/lib/libdigikamcore.so.6.4.0
#8  0x00007ffff7867591 in Digikam::PreviewLoadingTask::execute() () at /usr/lib/libdigikamcore.so.6.4.0
#9  0x00007ffff787d838 in Digikam::LoadSaveThread::run() () at /usr/lib/libdigikamcore.so.6.4.0
#10 0x00007ffff78a297e in  () at /usr/lib/libdigikamcore.so.6.4.0
#11 0x00007ffff5244922 in  () at /usr/lib/libQt5Core.so.5
#12 0x00007ffff5241530 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007ffff4d994cf in start_thread () at /usr/lib/libpthread.so.0
#14 0x00007ffff4eb12d3 in clone () at /usr/lib/libc.so.6
(gdb)
Comment 5 Maik Qualmann 2019-12-12 06:48:57 UTC
The backtrace is well known to us, we have been working on fixing the cause for several months. You can follow developments here: Bug 399923.
One more note, so far the crash has only been reported by users with an Intel CPU.

Maik

*** This bug has been marked as a duplicate of bug 399923 ***
Comment 6 r4c3 2019-12-12 08:44:01 UTC
Okay thank you very much for your work. 
Sorry for double posting this bug.

Best Regards and best wishes.
Martin
Comment 7 caulier.gilles 2019-12-23 06:11:38 UTC
Problem is fixed with new 7.0.0-beta1 through this long story from this bug

https://bugs.kde.org/show_bug.cgi?id=399923

You can test digiKam 7.0.0-beta1 with bundle available here:

https://download.kde.org/unstable/digikam/

Don't hesitate to give us a fresh feedback about his entry.

Thanks in advance

Gilles Caulier