https://bugs.kde.org/show_bug.cgi?id=410518
Bug ID: 410518
Summary: ~4 seconds after exiting with super-q, notice of crash
appears
Product: digikam
Version: 6.1.0
Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
I've seen this in at least 6.1 and confirmed it is in 6.2 . Seconds after
normally quitting, MacOS pops up a dialog "digikam quit unexpectedly",
requiring one to ignore, report..., or reopen.
STEPS TO REPRODUCE
1. Quit digikam.
OBSERVED RESULT
Crash dialog.
EXPECTED RESULT
No crash dialog.
CRASH REPORT
Process: digikam [32547]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier: digikam
Version: 6.2.0 (6.2.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: digikam [32547]
User ID: 502
Date/Time: 2019-08-02 09:39:40.288 -0400
OS Version: Mac OS X 10.14.6 (18G84)
Report Version: 12
Bridge OS Version: 3.6 (16P6568)
Anonymous UUID: A3B78802-9A75-4BA9-6ADB-E84F5DFAEEF3
Time Awake Since Boot: 750000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007ffee3700330
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [32547]
VM Regions Near 0x7ffee3700330:
STACK GUARD 00007ffedf701000-00007ffee2f01000 [ 56.0M] ---/rwx
SM=NUL stack guard for thread 0
--> Stack 00007ffee2f01000-00007ffee3701000 [ 8192K] rw-/rwx
SM=SHM thread 0
Submap 00007fff00000000-00007fff80000000 [ 2.0G] r--/rwx
SM=SHM machine-wide VM submap
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x00007ffee3700330 0 + 140732714189616
--
You are receiving this mail because:
You are watching all bug changes.
