SIGSEGV on macOS

[yulyugin]

Is there an existing issue for this?

• [x] I checked and did not find my issue in the already reported ones

Describe the bug

Crash on macOS while working with photos. I've seen it once so far, no clear reproducer.

Steps to reproduce

No clear reproducer.

Expected behavior

No response

Logfile | Screenshot | Screencast

darktable-segfault.txt

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.0.1

What OS are you using?

Mac

What is the version of your OS?

macOS 15.4.1

Describe your system

macOS 15.4.1, Apple M1, 16Gb.

Are you using OpenCL GPU in darktable?

I dont know

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

[ralfbrown]

No clear reproducer will make this hard to find and fix, especially without line-number info in the crash log....

The relevant part of the crash log (for the devs):

Thread 14 Crashed:: worker 3
0   libsystem_platform.dylib      	       0x1997172a8 _platform_memmove + 88
1   libdarktable.dylib            	       0x1011a2f58 _write_image + 32
2   libdarktable.dylib            	       0x1012c8d04 dt_imageio_export_with_flags + 3668
3   libdarktable.dylib            	       0x1011a2a8c _init_8 + 1268
4   libdarktable.dylib            	       0x1011a1da8 dt_mipmap_cache_get_with_caller + 1584
5   libdarktable.dylib            	       0x1011e3398 dt_image_load_job_run + 72
6   libdarktable.dylib            	       0x1011d9ce4 _control_job_execute + 196
7   libdarktable.dylib            	       0x1011da3b8 _control_work + 784
8   libsystem_pthread.dylib       	       0x1996ddc0c _pthread_start + 136
9   libsystem_pthread.dylib       	       0x1996d8b80 thread_start + 8

So the crash was while copying the result of running the pixelpipe into a thumbnail buffer. Possible buffer overflow due to incorrect resampling dimensions?

[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.

[yulyugin]

Haven't seen it for a while, closing.