Segfault on MacOS 15.6.1

[iyesin]

Is there an existing issue for this?

• [x] 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. …
6. 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.

[iyesin]

Second segfault just happened. Again, a new collection was opened. This time, again, a new collection was opened. After the import finished, I applied my style to several pictures from the collection and double-clicked on one of them. Immediately segfaulted. See attached report.

darktable_segfailt_again.txt.gz

[TurboGit]

Looks like a memory issue. It seems that your VM (8Gb) of memory is not enough and a malloc probably failed.

[iyesin]

@TurboGit The problem is it is not VM and the laptop itself have 36GB of RAM. Funny enough, exact same settings were used on Linux machine without a scratch.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.