Bug 512594

Summary:	Face scanning engine crashes on large files
Product:	[Applications] digikam	Reporter:	Casper A. Blom <Casper.A.Blom>
Component:	Faces-Engine	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	REPORTED ---
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version First Reported In:	8.8.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Casper A. Blom 2025-11-25 14:39:01 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
On a new desktop pc (Intel ultra 9 285k, 128GB RAM, 2*2TB SSD with 24TB HDD, RTX5080) as well as on old laptop (Dell XPS9510):
Running Face Scanning (settings all images, detect and recognition accuracy on 10 with face size large, searching through all 4000+ albums (>250k images), database: MySQL internal on MariaDB,  systematically crashes on an image folder that has XCF images (GIMP) and TIFF exports of rather large size >1GB. when these are excluded from scanning all goes fine.
I was able to narrow this problem down to those files by halving the collection to scan upon each crash, repeating and continuing until I was at specific individual folder and file level.

OBSERVED RESULT
The GUI crashes, while in the active processes list digikam ("Advanced digital photo management application") remains in memory at around 15GB. 
(When the task is ended, DigiKam can be relaunched and rerun ok.)

Windows itself remains rock-solid-ly operating, no need to restart OS.

EXPECTED RESULT
No GUI crash.

SOFTWARE/OS VERSIONS
Windows: 11 pro, 23H2 (build 22631.6199)

ADDITIONAL INFORMATION
I have been loving and activly supporting the DigiKam project for 10+ years - kudo's to you all, and especially to Gilles!

Kind regards, Casper

Comment 1 caulier.gilles 2025-11-25 14:55:16 UTC

Hi Casper,

The crash is certainly due to XCF format which is know to be problematic in time, and it will be complex to solve. TIFF files format are more robust and more easy to hack.

In all cases we need a debug trace of the crash under Windows following instructions here :

https://www.digikam.org/contribute/#windows-host-1

This will help us to locale the failure in the source code.

Thanks in advance for you help and your long time support.

Best regards

Gilles

Comment 2 caulier.gilles 2025-12-12 08:07:02 UTC

Casper,

Do you seen my last comment ?

Gilles Caulier