Cancelled render, can't do anything other than quit

Greetings all,

I am running the latest version 15.2.4 (free) and I started a render queue and after a few seconds I stop it. Resolve says job cancelled but I can't do anything other than quit. I can hover some menus but all options are grayed out. I chose quit and it asked if I want to save the project and then Resolve is stuck in a loop, using 34% CPU and 2.3Gb RAM.

Anyone has had that issue? I saw a thread back in version 12.5 that had that.

Cheers!

My experience is there is a lag between the time you cancel the render and the time the program becomes responsive to new input. It can take quite a while sometimes. You might try waiting it out once and see if this is the case.

Yes, I reported that a few days ago here. I think it only happens using the Nvidia encoder, but haven't double checked recently.

I just had this happen was well. It's not just laggy--it's stuck. I let it sit for more than 30 minutes. Many UI controls are disabled but some still work and the ones that do are as snappy as ever. The top menus are all still responsive but most of the items are disabled including the other pages. Task Manager says the system is basically idle.

The only thing I could do was quit and I couldn't do that also save the project. Answering "yes" the save prompt would just send it back to the stuck GUI. It wouldn't quit until I answered "no" and then it closed immediately.

I just had this happen was well. It's not just laggy--it's stuck. I let it sit for more than 30 minutes. Many UI controls are disabled but some still work and the ones that do are as snappy as ever. The top menus are all still responsive but most of the items are disabled including the other pages. Task Manager says the system is basically idle.

The only thing I could do was quit and I couldn't do that also save the project. Answering "yes" the save prompt would just send it back to the stuck GUI. It wouldn't quit until I answered "no" and then it closed immediately.

This is my experience on DaVinci Resolve Studio 18. Anyone know if this will ever be fixed? What's the purpose of the Stop Render button, if the program must be completely closed to actually make it stop?

I think this happens only with problematic renders, which would normally not finish anyway.
I can stop a render that would finish (most of mine do) and it stops and waits for my next input. So, it doesn't seem to be a simple bug.

The only thing I could do was quit and I couldn't do that also save the project. Answering "yes" the save prompt would just send it back to the stuck GUI. It wouldn't quit until I answered "no" and then it closed immediately.

I've occasionally had to cancel out a render when I realized (too late) that I had the wrong Data Burn-In, or -- worse -- I had a burn-in and wanted a clean render, or the wrong aspect ratio, whatever. Usually, it just quits after a second or two's hesitation, which is totally understandable.

Worst case, create a Diagnostics Log, park it on a file-sharing site, and post the link here. Maybe support can help. Just curious: is anything running in the background? We try to have absolutely nothing going on in the background, at least not until the render is completely done.