darktable-org / darktable-org/darktable

Segfault on MacOS 15.6.1

Open
#19,451 4 comments 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

I was scrolling up and down in a big-ish (1127 RAWs) import right after import was done (trying to find a duplicate because the Lighttable UI showed "0 images selected of 112_8_").

Steps to reproduce

It has rarely happened to me: actually, the second time in the year of using Darktable.
Both times, it was scrolling up and down several times while previews were still being generated.

  1. Start big-ish (1000+ RAWs) import as darktable ~/folder/with/raws
  2. Wait till "importing…" progress bar disappear
  3. Start scrolling down to the bottom
  4. Wait till thumbnails to render there and start scrolling up
  5. Sometimes darktable crashes.
Expected behavior

Continue working

Logfile | Screenshot | Screencast

Here is a CrashDump from the last segfault of mine.

darktable_2025.10.02.crashdump.gz

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

2.5.1

What OS are you using?

Mac

What is the version of your OS?

15.6.1 (24G90)

Describe your system

Model Name: MacBook Pro
Model Identifier: Mac15,7
Model Number: Z1AK001DLB/A
Chip: Apple M3 Pro
Total Number of Cores: 12 (6 performance and 6 efficiency)
Memory: 36 GB
System Firmware Version: 11881.140.96
OS Loader Version: 11881.140.96

Built-in and external monitors are used

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

Apple M3 Pro

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

Reproducible only with RAWs afaik.

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 by examining the attached crashdump and reproducing the reported sequence: import 1,000+ RAWs, wait for importing to finish, then scroll while thumbnails render. Compare behavior on macOS 15.6.1 with OpenCL enabled; done means identifying and preventing the segfault without interrupting normal browsing.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, macos
Domain
desktop
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.