darktable-org / darktable-org/darktable

[Crash] SIGSEGV in _event_button_release on macOS ARM64 (5.2.1)

Open
#19,636 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

darktable crashes unexpectedly during an action that appears to be related to the release of a mouse button (_event_button_release).

Steps to reproduce
  1. Open darktable
  2. Go to the Lighttable
  3. App shutdown and pops osx bug report
Expected behavior

No response

Logfile | Screenshot | Screencast

Process: darktable [5620]
Path: /Applications/darktable.app/Contents/MacOS/darktable
Identifier: org.darktable
Version: 5.2.1 (5.2.1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-11-01 21:27:23.4211 +0100
OS Version: macOS 15.6.1 (24G90)
Report Version: 12
Anonymous UUID: E3656D1C-26F7-2F14-DC64-0F22889921FA
Sleep/Wake UUID: F3607645-64F2-4A1D-B386-5C9BAD2EF82E
Time Awake Since Boot: 95000 seconds
Time Since Wake: 3321 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000138
Exception Codes: 0x0000000000000001, 0x0000000000000138
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [5620]
VM Region Info: 0x138 is not in any region. Bytes before following region: 4343676616
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 102e74000-102e88000 [ 80K] r-x/r-x SM=COW /Applications/darktable.app/Contents/MacOS/darktable
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdarktable.dylib 0x10382b500 _event_button_release + 624
1 libgtk-3.0.dylib 0x104cee5c4 _gtk_marshal_BOOLEAN__BOXED + 116
2 libgobject-2.0.0.dylib 0x104028514 g_closure_invoke + 204
3 libgobject-2.0.0.dylib 0x10403fca8 signal_emit_unlocked_R + 1284
4 libgobject-2.0.0.dylib 0x10403eefc signal_emit_valist_unlocked + 2064
5 libgobject-2.0.0.dylib 0x10403e6c0 g_signal_emit_valist + 64
6 libgobject-2.0.0.dylib 0x10403f22c g_signal_emit + 28
7 libgtk-3.0.dylib 0x104f567b8 gtk_widget_event_internal + 300
8 libgtk-3.0.dylib 0x104e2f2a0 propagate_event + 388
9 libgtk-3.0.dylib 0x104e2e6c4 gtk_main_do_event + 1048
10 libgdk-3.0.dylib 0x1033fe650 _gdk_event_emit + 64
11 libgdk-3.0.dylib 0x103422260 gdk_event_dispatch + 52
12 libglib-2.0.0.dylib 0x103ecd088 g_main_context_dispatch_unlocked + 236
13 libglib-2.0.0.dylib 0x103ecd3e0 g_main_context_iterate_unlocked + 484
14 libglib-2.0.0.dylib 0x103ecd664 g_main_loop_run + 120
15 libgtk-3.0.dylib 0x104e2e148 gtk_main + 92
16 libdarktable.dylib 0x10384476c dt_gui_gtk_run + 120
17 libdarktable.dylib 0x103889038 apple_main + 456
18 libdarktable.dylib 0x103887a44 -[AppDelegate applicationDidFinishLaunching:] + 664
19 CoreFoundation 0x1811d746c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 148
20 CoreFoundation 0x181266b28 ___CFXRegistrationPost_block_invoke + 92
21 CoreFoundation 0x181266a6c _CFXRegistrationPost + 436
22 CoreFoundation 0x1811a68b8 _CFXNotificationPost + 740
23 Foundation 0x182760680 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
24 AppKit 0x18510e1bc -[NSApplication _postDidFinishNotification] + 284
25 AppKit 0x18510df6c -[NSApplication _sendFinishLaunchingNotification] + 172
26 AppKit 0x18510c568 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 488
27 AppKit 0x18510c17c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 488
28 Foundation 0x182788e40 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 316
29 Foundation 0x182788c38 _NSAppleEventManagerGenericHandler + 80
30 AE 0x188bdb13c 0x188bd0000 + 45372
31 AE 0x188bdaa7c 0x188bd0000 + 43644
32 AE 0x188bd4044 aeProcessAppleEvent + 484
33 HIToolbox 0x18cbd6828 AEProcessAppleEvent + 68
34 AppKit 0x185105d38 _DPSNextEvent + 1456
35 AppKit 0x185aa4940 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
36 AppKit 0x1850f8be4 -[NSApplication run] + 480
37 libdarktable.dylib 0x103888314 main + 96
38 dyld 0x180d56b98 start + 6076

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.2.1 (5.2.1.0)

What OS are you using?

Mac

What is the version of your OS?

macOS 15.6.1 (24G90)

Describe your system

Architecture ARM-64 (Native)

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached macOS crash report and the _event_button_release entry point shown in the stack trace. Reproduce on macOS 15.6.1 with ARM64 hardware by opening darktable, entering Lighttable, and observing the shutdown crash. Done means the reported SIGSEGV no longer occurs during this sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, macos
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.