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

--- Comment #6 from [email protected] ---
Hi Gilles

I installed MS Debugview and captured the log during the crash. Here are
the last lines I got :










*digikam.facesengine: Finish computing face embedding in  0
 msdigikam.general: Found FacesEngine identity 56 for tag
36digikam.facesengine: FacePipelineEdit::writer(): bad
matdigikam.facesengine: FacePipelinePackageBase::~FacePipelinePackageBase:
Deleting package with serial number -1digikam.facesengine:
FaceClassifier::loadTrainingData: no training data
availabledigikam.facesengine: FaceClassifier::loadTrainingData: training
completed in  0 msdigikam.maintenance: Total is 1digikam.facesengine:
Creating new instance of DNNFaceDetectorYuNetdigikam.facesengine: Face
detection model: "YuNet" loadeddigikam.facesengine: Face detection model:
YuNet not loadeddigikam.facesengine: Failed to load YuNet model*

It seems that the YuNet model is one of the causes... Any remediation
possible ?

I haven't installed Visual Studio yet, because I don't know much about
development tools.
Digikam Database is SQLite without WAL.

Just a personal question : do you speak French ??

Philippe Bezard-Falgas


Le sam. 12 sept. 2026 à 07:29, <[email protected]> a écrit :

> https://bugs.kde.org/show_bug.cgi?id=525042
>
> --- Comment #5 from [email protected] ---
> 1/ Please install the debugview tool from Microsoft to capture the debug
> statements.
> 2/ To really seen where the crash occurs, you need to install a debugger
> and
> capture the crash dump. Installeing the digiKAm debug version (more heavy)
> will
> help to localize the source code.
>
> All is explained in the contrib page from the project:
>
> https://www.digikam.org/contribute/#windows-host
>
> https://www.digikam.org/contribute/#using-visual-studio
>
> Note: under Linux and macOS, the problem is not reproducible.
>
> Q: which kind of database did you use ?
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to