DARKTABLE | DIFFUSION | ERROR ~ tiling failed for module diffuse |

Software darktable
1

tiling failed for module diffuse the output most likely will be ok but you might want to check

Good afternoon! I am glad to write here again, as I am sure that I will be helped with warmth, kindness, and understanding!

I’m writing through a translator.

While processing some time ago, I started using a new processing process that includes diffusion.

Since my computer is very weak for a large number of iterations, I avoided this process. Now I started using it with a few iterations.

Recently, I encountered an error. I tried changing the module settings, but the image always looked different. I set the module to render 70 photos per day and left, but when I returned 12 hours later, only 54 photos had been rendered.

I fixed the processing without this module. And I forgot about the error for a while. Now I’ve processed about 300 photos, and only at the end did I notice that it was throwing an error during rendering.

I need a different solution. I’ve just thought that maybe Dithering before the diffusion module would help me? I haven’t tried it yet.

Can you tell me what ideas you have for fixing the error? The photos that were processed for 12 hours looked the same, even if something was skipped inside… Maybe I should force-disable the re-processing? After the error, only a reboot helps… That’s why I didn’t take a screenshot. I’ve attached a screenshot of the module settings. Thank you all!

WINDOWS 10 DT 5.4.1

2026-05-18_20-36-12
2026-05-18_20-36-12661×694 49.1 KB

2

Are you using opencl? what’s you system (RAM, GPU, GPU RAM). Console output of darktable -d pipe -d tiling would be helpful I guess

1 Like
3

Hi! Sorry, I’m not very good at this. Is that enough for you?

2026-05-18_22-30-43
2026-05-18_22-30-43826×488 20.8 KB

4

I can use CPU-Z need?

It probably wouldn’t hurt to add. I’m exaggerating… Sometimes I use 15 iterations, which take a long time to load, but I use them when I blur. In this case, I think the problem lies in the lower part of the module, where the edges are bound.

5

I figured it out, it seems to be the central radius. I restarted my computer and was able to export without the Central Radius. I wonder how this can be overcome?

6

As I said, for the devs to know if this is a new or an old bug which might already be fixed in the upcoming 5.6. release, you need to run darktable from a terminal/powershell with

darktable.exe -d pipe -d tiling

and paste the output when it’s crashing here.

A graphics card for OpenCL will help with the speed for sure. You should think about getting one.