gi-man

The issue occurred with libgtk-3-0.dll. Is this the first crash?

I'm in Win11 with Nvidia 512.95. I've been using "memory size and transfer" and I had zero problems with GPU. Yesterday I was exporting ~40 images that used the new...

> I don't get crashes myself, but the system freezes in the darkroom (with "working..." overlaid on the image) and eventually the UI becomes unresponsive and I have to `kill...

@jenshannoschwalm I will keep commenting in this thread instead of the other one. Last night I was thinking the difference between 0 and 1 in the headroom could be something...

I had a small amount of time to look into this today. -d opencl -d verbose with headroom 0 and headroom at 1 looked identical. I'm still in same build...

I used the same image. I turned on/off the highlight recovery module with GL using 4 iterations just to force some GPU usage. headroom=1 https://pastebin.com/CyBvVsN3 headroom=400 https://pastebin.com/kZzXTF5m headroom=0 https://pastebin.com/09MQqhdB

Just to share my current observations: I've been trying different things to see if I can cause a change. I think I did manage to make it worst via changing...

@jenshannoschwalm FYI Nvidia released a new driver today, 516.59. I'm on 4.1.0+19~g387e05538 using memory size on and large resources. I modified darktablerc to: cldevice_v4_nvidiageforcertx3060_id0=0 and the problem returns. cldevice_v4_nvidiageforcertx3060_id0=1 and...

The part that has me thinking the most was the export via the lighttable vs darkroom. The export is a full use of the pipeline and it processing the image...

Ive been using Fedora 36 on my system, but I noticed that nvidia updated the windows driver to 516.94. I switched to windows to test it. It continues to crash...