Project

General

Profile

Bug #12030

Spontaneous crash at `dt_opencl_write_buffer_to_device` when exporting

Added by Sarge Borsch over 1 year ago. Updated over 1 year ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
OpenCL
Target version:
-
Start date:
02/24/2018
Due date:
% Done:

20%

Affected Version:
2.4.1
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

This bug sometimes reproduces on any of the raw shots from Sony A5100.
Both times when it happened, I was exporting to PNG, 8 bit, max compression, output profile = sRGB, no resizing.
I am attaching one of the shots where (IIRC) this actually happened, together with the XMP profile, but I think there's nothing special about this shot. Plus the two crash reports generated by macOS (apparently in both of them the crash happens at `dt_opencl_write_buffer_to_device`).

I did not enable "automatic graphics switching" in the OS settings; and the laptop was plugged in the power source in both cases.

DSC00461.ARW.xmp (11.1 KB) Sarge Borsch, 02/24/2018 02:29 PM

DSC00461.ARW.xz (20.4 MB) Sarge Borsch, 02/24/2018 02:29 PM

trace1.txt Magnifier (123 KB) Sarge Borsch, 02/24/2018 02:30 PM

trace2.txt Magnifier (139 KB) Sarge Borsch, 02/24/2018 02:30 PM

History

#1 Updated by Ulrich Pegelow over 1 year ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

I tried with your image but I could not reproduce your issue here on my NVIDIA GPU. I have no personal experience with the Intel OpenCL implementation that drives your system.

FWIW: your crash is triggered in the lens correction module.

#2 Updated by Sarge Borsch over 1 year ago

Ulrich Pegelow wrote:

I have no personal experience with the Intel OpenCL implementation that drives your system.

If I got that right, my system should also use NVIDIA GPU. But in this case Intel was used (judging by the backtrace). This in itself is strange, because "automatic graphics switching" was disabled and "very fast GPU" OpenCL scheduling mode was chosen in darktable settings. Maybe it should not had been using Intel path here at all?

#3 Updated by Ulrich Pegelow over 1 year ago

You can force darktable to only use your NVIDIA GPU. It's a bit complicated as this is not a usual situation:

1) switch OpenCL scheduling mode to "default"

2) go into your darktablerc and look for parameter opencl_device_priority. Depending on whether your NVIDIA GPU is registered as number 0 or number 1 you either set this parameter to "0/!0/0/0" or "1/!1/1/1". Start darktable with -d opencl to find out darktable's device number of your NVIDIA GPU.

Also available in: Atom PDF