Darktable crashes with no certain action mostly by itself, sometimes while changing between modules but mostly by itself

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 with no certain action mostly by itself, sometimes while changing between modules but mostly by itself.

Crash report:

Translated Report (Full Report Below)

Process: darktable [2127]
Path: /Applications/darktable.app/Contents/MacOS/darktable
Identifier: org.darktable
Version: 5.6.0 (5.6.0.0)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: org.darktable [1539]
User ID: 501

Date/Time: 2026-07-17 11:43:36.4604 +0200
Launch Time: 2026-07-17 09:52:53.9183 +0200
Hardware Model: Mac14,13
OS Version: macOS 26.5.2 (25F84)
Release Type: User

Crash Reporter Key: 51B7F7BF-EA9A-D098-0931-E8AA4CB0DD65
Incident Identifier: 100AB1AD-8D10-432F-A8AD-C733986FE75F

Sleep/Wake UUID: 7F762F89-6265-4A00-896A-D19FAB4A4EC7

Time Awake Since Boot: 10000 seconds
Time Since Wake: 2 seconds

System Integrity Protection: enabled

Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6
Terminating Process: darktable [2127]

following in added file

crash-report-17-07-26.rtf

Steps to reproduce

Waiting

Expected behavior

not crash and also not be so slowed down

Logfile | Screenshot | Screencast

No response

Commit

Mostly not doing any action at all

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.6.0.

What OS are you using?

Mac

What is the version of your OS?

25.6.2

Describe your system

Apple M2 Max, 35 GB RAM

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

Start by examining the attached crash report for darktable 5.6.0 on Apple M2 Max/macOS, focusing on the main-thread SIGABRT. There is no named source file, test, or reliable reproduction; establish a reproducible crash while idle or switching modules, then verify that the failure and reported slowdown are resolved.