https://bugs.kde.org/show_bug.cgi?id=425723
Bug ID: 425723
Summary: Digikam crashes after a while when detecting faces
using multiple CPU cores
Product: digikam
Version: 7.0.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Faces-Detection
Assignee: digikam-bugs-n...@kde.org
Reporter: simon.westers...@iki.fi
Target Milestone: ---
Created attachment 131132
--> https://bugs.kde.org/attachment.cgi?id=131132&action=edit
gdb backtrace after the crash
SUMMARY
Digikam crashes when detecting faces using multiple CPU cores
STEPS TO REPRODUCE
Not sure if this is reproducible by all, but this is what I did.
1. Add a large collection of photos (over 27000 JPEG files) from an external
hard-drive.
2. In the People tab, change the setting "Work on all processor cores" to true.
3. For workflow, use "Detect faces" and "Skip images already scanned"
4. Then start the scanning by clicking "Scan collection for faces".
OBSERVED RESULT
Digikam crashes after a while. The GUI showed nothing helpful. The window died.
EXPECTED RESULT
Digikam should not crash. If there are problems with a photo, or something
else, it should probably just be skipped, so that the scan can complete.
SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Linux kernel 5.8.1-3-MANJARO
(available in About System)
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
ADDITIONAL INFORMATION
The scan of my collection crashed digikam several times, so I restarted and
tried again. Some scans could proceed further than others. E.g. the first scan
crashed after going through less than 5% of the collection. The other scans
covered some 20-30% each.
The crash comes from a segmentation fault. On the latest rerun, I used GDB to
get a backtrace. See the backtrace attached.
The crash did not seem to be due to memory pressure. I have 16 GB of memory and
during the scan, the whole system only used around 4 GB.
I did not test the scanning without the "Work on all processor cores" yet.
--
You are receiving this mail because:
You are watching all bug changes.
