opencl_mandatory_timeout in dt 5.6

After upgrade dt 5.4 to 5.6 the response in darkroom became very slow.
When shifting a slider, the the result needs some seconds to get visible and some more time for the histogram.

My hardware is some years old, but worked fine with dt 5.4: NVIDIA GeForce GTX 1060 6GB.

Starting with command “darktable -d opencl” there are a lot of errors:

[opencl_lock_device] reached opencl_mandatory_timeout trying to lock mandatory device, fallback to CPU

And sometimes:

Error: process CL0 [full] rawoverexposed

In darktablerc I changed

opencl_mandatory_timeout=200

… to 300; no effect.

My system was Ubuntu 24.04 LTS with linux kernel 6.8 and CUDA-driver.
Yesterday I upgraded the distribution to 26.04 LTS with newer kernel 7 and native cuda-support. Also no effect, same errors.

The “DT Performance Analyser” from command “darktable-cli” ran without errors.

What can I do?

Please post the output from darktable-cltest in .txt format.

Also, flatpak?

1 Like

That analyser won’t help here.

There have been a few issues fixed for 5.6.1 and on master that will very likely fix your issue.

2 Likes

dt_cltest_output.txt (3.8 KB)

When will 5.6.1 be released?
Can I wait or should I try to compile the master-branch?
I never compiled dt before.

Hi Frank, welcome to the forum, hope you will like it and feel being at home here. Compiling darktable on Linux is not a big deal. There is a straight forward guide on how to do it.
Best regards :wave:

1 Like

Thank you for the guide. Compiling is complete. Only “libpotrace-dev” was missing, had to install manually.
The compiled dt-version is much faster, then the installed 5.6.
Less errors, when started with /opt/darktable/bin/darktable -d opencl.
Only errors when using the raw-overexposure-indicator.

3 Likes

Thanks for reporting. Will take care of this.

1 Like