Bug #11248

Magick: abort due to signal 7 (SIGBUS) "Bus Error"

Added by Fran├žois Guerraz over 2 years ago. Updated over 2 years ago.

Closed: upstream
Target version:
Start date:
Due date:
% Done:


Affected Version:
other GNU/Linux
hardware architecture:


On Arch 64 with Beignet and GTK+ 3.22.

Not always but often, I get this crash when I double click an image in the light table.


Stack trace of thread 3157:
#0 0x00007f75a626204f raise (
#1 0x00007f75a626356a abort (
#2 0x00007f75a147d620 MagickPanicSignalHandler (
#3 0x00007f75a65de080 __restore_rt (
#4 0x00007f75a63577cf __memmove_avx_unaligned_erms (
#5 0x00007f758e5756b0 cl_mem_copy_image_region (
#6 0x00007f758e573e1e cl_enqueue_write_image (
#7 0x00007f758e56af77 clEnqueueWriteImage (
#8 0x00007f758e7cd06a clEnqueueWriteImage (
#9 0x00007f75a68bdea6 dt_opencl_write_host_to_device_raw (
#10 0x00007f75a68be00a dt_opencl_write_host_to_device_rowpitch_non_blocking (
#11 0x00007f75a68e3a3d dt_dev_pixelpipe_process_rec (

gdb.txt Magnifier - gdb bt full (50.8 KB) Fran├žois Guerraz, 10/20/2016 08:38 AM


#1 Updated by John K over 2 years ago

I'm also getting a crash, either when opening an image from lighttable to darkroom, or sometimes when editing in darkroom. With OpenCL enabled, either via beignet (intel integrated graphics) or nvidia. On Arch 64bit, with darktable 2.0.7 and 2.2.0rc0. This also happened on a previous version (not sure which, maybe 2.0.6). Crash message is always:

"Magick: abort due to signal 7 (SIGBUS) "Bus Error"..."

What other outputs would be helpful?

#2 Updated by John K over 2 years ago

With the latest version of darktable (2.2.0) and all the opencl and graphics drivers as of the 2.2.0 darktable release, it has not crashed yet. So hopefully this means whatever was going wrong is fixed, perhaps on the graphics/opencl driver side.

#3 Updated by Roman Lebedev over 2 years ago

  • Status changed from New to Closed: upstream

Wait, beignet?

#4 Updated by Roman Lebedev over 2 years ago

  • Target version set to 2.4.0

#5 Updated by John K over 2 years ago

Ah, sorry, forgot that I have both beignet and nvidia. I see that beignet has been blacklisted (when running darktable-cltest). Perhaps there was an interaction with nvidia that caused this problem? When was this changed? Like I said, still crashed on 2.2.0rc0.

I know with the nvidia card enabled (using optirun or primusrun) darktable-cltest used to list both the intel and nvidia opencl as available, now it is just nvidia. There are too many moving pieces, so it is hard to say what did it, but after a few hours of editing with darktable 2.2.0 and opencl turned on with nvidia, it did not crash at all. Great to have the opencl speed back.

Also available in: Atom PDF