Darktable often ignores denoising during export

Hi everyone,

I have recently noticed a problem where darktable seems to ignore every denoising-related module on export. Like the output contains my edits, but is not denoised at all. It doesn’t apply modules like astrophoto denoise, denoise (profiled) or contrast equalizer.

I noticed it may have something to do with high RAM usage, usually when it’s around 75% (16GB total) or more before clicking export. Sometimes restarting darktable helps, but sometimes I have to reboot my laptop to have denoising applied to the exported image.

I tried running darktable.exe -d all, but the terminal output is empty and no log is being written anywhere (at least according to Everything search engine with live a list of recently created/modified files)
How do I debug again? :sweat_smile:
Any ideas what could be wrong?

See faq | darktable section “Windows” for the location of log file.

2 Likes

Ok, thanks I forgot about the change of the log file…

Well, my guess was true, memory alloc fails:
(crash on export)

41.7467 Trouble: [denoise (profiled)] unable to allocate working memory (DSC_3318.NEF 1771)
41.8255 [dev_pixelpipe] took 0.196 secs (0.234 CPU) [export] processed `denoiseprofile.1' on CPU, blended on CPU
Magick: caught exception 0xC0000005 "Access violation"...

(different crash on opening darkroom)

9.9026 couldn't write scharr mask CL CL0 [full]                                        DT_OPENCL_SYSMEM_ALLOCATION
Magick: caught exception 0xC0000005 "Access violation"...

(export complete, no denoising)

23.4804 Trouble: [denoise (profiled)] unable to allocate working memory (DSC_3318.NEF 1771)
23.5485 [dev_pixelpipe] took 0.165 secs (0.281 CPU) [export] processed `denoiseprofile.1' on CPU, blended on CPU