darktable-org / darktable-org/darktable
Random segfaults
Nobody has claimed this yet.
- 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
Copy and pasted some history between pics and it crashed. Seemed rather random
Steps to reproduce
- Ctrl+C on image
- Ctrl+V crash. Doesn't happen all the time
Expected behavior
not crash
Logfile | Screenshot | Screencast
Thread 1 (Thread 0x7f9510a87d80 (LWP 2946449) "darktable"):
#0 0x00007f9528aa07f2 in ??? () at /usr/lib/libc.so.6
#1 0x00007f9528a9481c in ??? () at /usr/lib/libc.so.6
#2 0x00007f9528a94864 in ??? () at /usr/lib/libc.so.6
#3 0x00007f9528b11a0e in write () at /usr/lib/libc.so.6
#4 0x00007f952bb5b3a9 in ??? () at /usr/lib/libglib-2.0.so.0
#5 0x00007f952edfa335 in dt_lua_async_call_alien_internal (call_function=call_function@entry=0x7f94dde1b9c0 <FUNCTION.18> "_fire_darkroom_image_loaded_event", line=line@entry=1222, pusher=0x7f952edfcc70 <dt_lua_event_trigger_wrapper>, nresults=nresults@entry=0, cb=cb@entry=0x0, cb_data=cb_data@entry=0x0, arg_type=LUA_ASYNC_TYPENAME) at /run/media/nuno/vms_ssd/builds/darktable/src/lua/call.c:550
data = 0x56142887c1b0
ap = {{gp_offset = 48, fp_offset = 1082975688, overflow_arg_area = 0x7fff803ef1d0, reg_save_area = 0x7fff803ef120}}
cur_type = LUA_ASYNC_DONE
closure =
_g_boolean_var_12 =
#6 0x00007f94dde10ce0 in _fire_darkroom_image_loaded_event (clean=false, imgid=) at /run/media/nuno/vms_ssd/builds/darktable/src/views/darkroom.c:1222
#7 _dev_load_requested_image (user_data=0x561421c84430) at /run/media/nuno/vms_ssd/builds/darktable/src/views/darkroom.c:1367
dev =
imgid =
old_imgid =
nb_iop =
option = "\220\363>\200\377\177\000\000\000\000\000\000\000\000\000\000P\362>\200\000\000\000\000\360s\005.\225\177\000\000\200\363>\200\377\177\000\000\020\361>\200\377\177\000\000\002\000\000\000\000\000\000\000\300\363>\200\377\177\000\000\002", '\000' <repeats 11 times>, "\001\000\000\000\001\000\000\000\024V\000\000\360\364>\200\377\177\000\000\260\364>\200\377\177\000\000\000א\026Kr\331\327\300\362>\200\377\177\000\000\002\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\260\363>\200\377\177\000\000\020\000\000\000\000\000\000\000P\363>\200\377\177\000\000R\275\354\033\225\177", '\000' <repeats 18 times>, "\360s\005.\225\177\000\000\220"...
active_plugin =
#8 0x00007f952bafec76 in ??? () at /usr/lib/libglib-2.0.so.0
#9 0x00007f952bb00ed7 in ??? () at /usr/lib/libglib-2.0.so.0
#10 0x00007f952bb01217 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#11 0x00007f952ed46e53 in dt_gui_gtk_run (gui=0x561420f75ae0) at /run/media/nuno/vms_ssd/builds/darktable/src/gui/gtk.c:1824
widget =
allocation = {x = 0, y = 0, width = 1267, height = 818}
#12 0x00005613fbfa7265 in main (argc=, argv=) at /run/media/nuno/vms_ssd/builds/darktable/src/main.c:158
exitcode =
[Inferior 1 (process 2946449) detached]
backtrace written to /tmp/darktable_bt_K9Z6S3.txt
Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
fish: Job 1, '/opt/darktable-test/bin/darktab…' terminated by signal SIGABRT (Abort)
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.7.0+192~g59ed384a10-dirty
What OS are you using?
Linux
What is the version of your OS?
Arch Linux
Describe your system
RTX 3080 10GB, 5950X, 64GB RAM
Are you using OpenCL GPU in darktable?
Yes
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the intermittent Ctrl+C/Ctrl+V history-copy crash on Linux with the reported darktable build. Inspect the backtrace entries in src/lua/call.c:550 and src/views/darkroom.c:1222 and 1367, then use the available crash log to narrow the fault. Done means the reported workflow no longer produces a segmentation fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100