Forgive me, I'm not very technical, so I apologize if this is the wrong place to post this. I am using Digikam v5.9.0 on 64-Bit Windows 10. I've never experienced this issue before, and it may be related to the same Bug 392134 - SIGSEGV While Scanning Faces [patch] (https://bugs.kde.org/show_bug.cgi?id=392134). Whenever I have Digikam scan for faces, it reaches about 29% and then just crashes. I looked for the digikam crash logs and couldn't find any. I was only able to find the Windows Event Viewer and this is what it resulted in: Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x5aaeb54e Faulting module name: libdigikamcore.dll, version: 0.0.0.0, time stamp: 0x5aaeb524 Exception code: 0xc0000005 Fault offset: 0x00000000001359a4 Faulting process id: 0x6420 Faulting application start time: 0x01d3cabaa8cde954 Faulting application path: D:\Program Files\digiKam\digikam.exe Faulting module path: D:\Program Files\digiKam\libdigikamcore.dll Report Id: 4c358776-a59b-4dee-a25d-b5ae2c6b2f62 Faulting package full name: Faulting package-relative application ID: - System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2018-04-02T19:51:09.891172700Z EventRecordID 354488 Channel Application Computer DESKTOP Security - EventData digikam.exe 0.0.0.0 5aaeb54e libdigikamcore.dll 0.0.0.0 5aaeb524 c0000005 00000000001359a4 6420 01d3cabaa8cde954 D:\Program Files\digiKam\digikam.exe D:\Program Files\digiKam\libdigikamcore.dll 4c358776-a59b-4dee-a25d-b5ae2c6b2f62 Interestingly, the crash entry in the windows event log is consistently always preceded by 2 "Information"-level entries with the source "dbupdate" with the following message: The description for Event ID 0 from source dbupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Service started Followed by 10-20 "Error"-level entries with source "VSS" with the following message: Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine returned E_INVALIDARG. Routine details GetSnapshot({00000000-0000-0000-0000-000000000000},000001D4BFDF2C30). Operation: Get Shadow Copy Properties Context: Execution Context: Coordinator - System - Provider [ Name] VSS - EventID 12294 [ Qualifiers] 0 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2018-04-02T19:50:48.616200600Z EventRecordID 354487 Channel Application Computer DESKTOP Security - EventData {b5946137-7b9f-4925-af80-51abd60b20d5} GetSnapshot({00000000-0000-0000-0000-000000000000},000001D4BFDF2C30) Operation: Get Shadow Copy Properties Context: Execution Context: Coordinator 2D20436F64653A20434F52434F4F524330303030303734352D2043616C6C3A20434F52434F4F524330303030303639322D205049443A202030303033313034382D205449443A202030303033303835362D20434D443A2020433A5C57494E444F57535C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820 -------------------------------------------------------------------------------- Binary data: In Words 0000: 6F43202D 203A6564 43524F43 43524F4F 0010: 30303030 35343730 6143202D 203A6C6C 0020: 43524F43 43524F4F 30303030 32393630 0030: 4950202D 20203A44 33303030 38343031 0040: 4954202D 20203A44 33303030 36353830 0050: 4D43202D 20203A44 575C3A43 4F444E49 0060: 735C5357 65747379 5C32336D 76737376 0070: 78652E63 20202065 7355202D 203A7265 0080: 656D614E 544E203A 54554120 49524F48 0090: 535C5954 45545359 53202C4D 533A4449 00a0: 352D312D 2038312D In Bytes 0000: 2D 20 43 6F 64 65 3A 20 - Code: 0008: 43 4F 52 43 4F 4F 52 43 CORCOORC 0010: 30 30 30 30 30 37 34 35 00000745 0018: 2D 20 43 61 6C 6C 3A 20 - Call: 0020: 43 4F 52 43 4F 4F 52 43 CORCOORC 0028: 30 30 30 30 30 36 39 32 00000692 0030: 2D 20 50 49 44 3A 20 20 - PID: 0038: 30 30 30 33 31 30 34 38 00031048 0040: 2D 20 54 49 44 3A 20 20 - TID: 0048: 30 30 30 33 30 38 35 36 00030856 0050: 2D 20 43 4D 44 3A 20 20 - CMD: 0058: 43 3A 5C 57 49 4E 44 4F C:\WINDO 0060: 57 53 5C 73 79 73 74 65 WS\syste 0068: 6D 33 32 5C 76 73 73 76 m32\vssv 0070: 63 2E 65 78 65 20 20 20 c.exe 0078: 2D 20 55 73 65 72 3A 20 - User: 0080: 4E 61 6D 65 3A 20 4E 54 Name: NT 0088: 20 41 55 54 48 4F 52 49 AUTHORI 0090: 54 59 5C 53 59 53 54 45 TY\SYSTE 0098: 4D 2C 20 53 49 44 3A 53 M, SID:S 00a0: 2D 31 2D 35 2D 31 38 20 -1-5-18 After the series of VSS errors, the Digikam application error appears (as posted above). I'm not event sure I'm sharing the right info or if it's in the right place. I tried the IRC channel and there wasn't much activity there and the website urges you to submit these kinds of things here. Basically, the face scanning feature just DOES NOT work beyond 29%. Not sure what I can do to fix it.
This crash was fixed in bug 399923. Maik