Prior to this upgrade, i don’t think i’d ever had Darktable crash (close unexpectedly) a single time, and i’ve been using it frequently for at least 2 years now.
Since this upgrade, i’ve had it crash (close unexpectedly) several times when processing images. Nothing logged in Windows Event Viewer.
Because Darktable doesn’t save changes as you go along, all changes are lost when this occurs, potentially 20-30min into processing.
I’ve noticed if i simply visit Lighttable and re-load the image i’m currently working on it saves the steps I’d previously done - So i’m going to recommend either Darktable save steps as you’re processing, or give the user a save button? - (maybe that already exists and i haven’t noticed?)
This was occurring without a lot of predictability until recently. Generally each time this occurs it’s not specific to a module i’m using, but i’ve been able to “cause” this to occur repeatedly on a particular image within some steps of using Graduated Density, although again, i don’t think it has anything to do with that Module as i believe I was using other modules when this crash occurred when processing other images.
After googling i’d seen suggestions to update the display driver, which honestly i was reluctant to do as i can run any graphics or video editing program, old or new FPS game, flawlessly, there is nothing going on with this machine at all. Despite that i upgraded my (NVIDIA) drivers to 531.18, no difference, i then did a clean install of 531.18, no difference. I re-booted between each driver install.
If you are to run cmd/command from anywhere the syntax for an assumed default-installation location would be:
“C:\Program Files\darktable\bin\darktable.exe” -d all
After that and some googling, it appears the log file is @ C:\Users\\AppData\Local\Microsoft\Windows\INetCache\darktable\darktable-log.txt
I have a clean log isolated to the minimum steps involved to cause this to re-occur, after viewing the file it looks like i’d need to redact it a bit but the last few lines are consistent regardless, ending in the “Access violation.”
81.394313 [opencl memory] device 0: 14838720 bytes (14.2 MB) in use
81.394416 [dev_pixelpipe] took 0.005 secs (0.000 CPU) [full] processed
base curve' on GPU, blended on GPU [dev_pixelpipe] module input color profile’ min: (1.066164; -47.160866; -33.037830) max: (110.451675; 39.998413; 488.294708) [preview]
81.396183 [process CPU] preview nlmeans. IN ( 0/ 0) 873x 573 scale=1.00. OUT ( 0/ 0) 873x 573 scale=1.00, final 873x573, backbuf 873x573
Magick: caught exception 0xC0000005 “Access violation”…Magick: caught exception 0xC0000005 “Access violation”…