https://bugs.kde.org/show_bug.cgi?id=523211
Bug ID: 523211
Summary: Crash on start on Windows 10 (Exception code:
0xc0000005 Fault offset: 0x0000000000000000) with
today's Beta release
Classification: Applications
Product: digikam
Version First 9.2.0
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
After updating, and running Digikam- it showed no visual sign of start. I
checked resource management, and saw 15% CPU on an I7, but then it basically
killed itself or the OS terminated it. Several tries with the same result.
Reboot didnt change behaviour. Reversion to prior release worked.
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Nothing has changed on my end. I dont get a failing module code- just a memory
access error code. On occasion this can be a CPU affinity problem (setting),
but given that this is new, and revert to a release from 4 days ago solved
this, pretty clear that a new library is involved that isnt well behaved on
some systems.
Faulting application name: digikam.exe, version: 9.2.0.0, time stamp:
0x6a30dc2a
Faulting module name: ntdll.dll, version: 10.0.19041.6456, time stamp:
0x7ec9c15d
Exception code: 0xc0000005
Fault offset: 0x000000000005234e
Faulting process id: 0x2c48
Faulting application start time: 0x01dd16be8bb7c90a
Faulting application path: D:\Program Files\digiKam\digikam.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
--
You are receiving this mail because:
You are watching all bug changes.
