Bug 419192 - Crash when updating fingerprints on windows
Summary: Crash when updating fingerprints on windows
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Similarity (other bugs)
Version First Reported In: 6.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-24 18:41 UTC by matthew
Modified: 2022-01-02 10:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 7.5.0
Sentry Crash Report:


Attachments
Windows Error Reporting files (56.26 KB, application/octet-stream)
2020-03-24 18:41 UTC, matthew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description matthew 2020-03-24 18:41:32 UTC
Created attachment 126988 [details]
Windows Error Reporting files

SUMMARY

Files are being accessed on an samba share from a NAS using a mapped drive. When I attempt to update the fingerprints, it gets to 47% and crashes.

STEPS TO REPRODUCE
1. Add location
2. Update fingerprints
3. crash

OBSERVED RESULT
Crash

EXPECTED RESULT
No Crash

SOFTWARE/OS VERSIONS
Windows: Win 10 Home

ADDITIONAL INFORMATION

Info from the event viewer

Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x5cb43812
Faulting module name: ntdll.dll, version: 10.0.18362.719, time stamp: 0x64d10ee0
Exception code: 0xc0000028
Fault offset: 0x00000000000fbf98
Faulting process id: 0x3170
Faulting application start time: 0x01d60209d627de79
Faulting application path: C:\Program Files\digiKam\digikam.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 3b6cc6a2-985a-4226-b0b9-6f67b5a9cca2
Faulting package full name: 
Faulting package-relative application ID: 


Also attaching the error report from the crash. Not sure how useful this info is. But I hope it is.
Comment 1 matthew 2020-03-24 18:49:00 UTC
I just noticed the latest version available (which I thought the version drop down was odd when I filled out the report). Usually chocolatey is good about keeping the latest version available to install, this is not the case.

I updated to 6.4 and re-initiated the fingerprint, and it's now sitting on 49% and scanning more images. I'll open a new case if it dies again (as I suspect it'll be a different error).