| Summary: | ~4 seconds after exiting with super-q, notice of crash appears | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Joseph Reagle <joseph.2011> |
| Component: | Bundle-MacOS | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 6.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Homebrew (macOS) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | 6.3.0 | |
| Sentry Crash Report: | |||
*** This bug has been marked as a duplicate of bug 407235 *** Please test with the 6.3.0 pre-release PKG for MacOS to see if this problem is reproducible : https://files.kde.org/digikam/ Gilles Caulier Gilles, currently there are no pre-release OSX packages available... Maik yes, i seen. The last upload have been broken. there are plenty of thunderstorms here when make perturbations on the network. I re-upload the file now. I will be online in one hour. Gilles Crash report still present
Process: digikam [29398]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier: digikam
Version: 6.3.0 (6.3.0-git)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: digikam [29398]
User ID: 502
Date/Time: 2019-08-05 08:19:17.875 -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: 1000000 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 0x00007ffeea24a330
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [29398]
VM Regions Near 0x7ffeea24a330:
STACK GUARD 00007ffee624b000-00007ffee9a4b000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0
--> Stack 00007ffee9a4b000-00007ffeea24b000 [ 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 ??? 0x00007ffeea24a330 0 + 140732826690352
...
This bug report was closed as duplicate, please comment in the older bug report. (Bug 407235) Maik *** This bug has been marked as a duplicate of bug 407235 *** Fixed with bug #407235 |
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