Blackmagic Forum

I have this weird issue, which started, I think, on version 19. Each session, when I first open the delivery page (or via the "Add to render queue using" function), Resolve becomes unresponsive for some time, and often crashes. This is especially annoying if the project was last saved while at the Delivery page. That makes the app freeze or crash on opening the project, and often requires several tries before the project can be opened.
If the first switch was successful, all subsequent navigation between pages is seamless.

At first, I thought that the culprit might be the Voukoder render plugin. I removed it when Resolve could natively render ProRes, but the issue remained.
Then I thought that it might be caused by mapped network drives in conjunction with the "Automatically attach drives" tick in preferences. However, unticking the option and leaving only two local drives (one with the database and projects, the other with media) added to Media Storage Locations didn't help.

I'm out of ideas, so any help is appreciated.

Here's the log after the latest crash, and system info https://drive.google.com/drive/folders/ ... sp=sharing

Brief system specs are in my signature.

I don't really see anything that looks like that in your logs.

If you can make it happen again, note the date and time (PC clock time) and if it does eventually load, make a diagnostics log immediately after that. If it crashes, make a log immediately after restarting, and note that when you send the log.

Dwaine Maggart wrote:I don't really see anything that looks like that in your logs.

If you can make it happen again, note the date and time (PC clock time) and if it does eventually load, make a diagnostics log immediately after that. If it crashes, make a log immediately after restarting, and note that when you send the log.

This is what I did, actually, I made the log immediately after the restart from the crash. I'll try again tomorrow, it crashes quite often.

The temporary freeze is a known issue and is related to the number of render jobs in the database. The more render jobs you have across all projects, the longer the delay when opening the Deliver tab for the first time. A workaround is to delete the render jobs from all projects. It's unclear why this hasn't been fixed after two years.

Here is a related thread
viewtopic.php?f=21&t=184019

Dwaine Maggart wrote:I don't really see anything that looks like that in your logs.

If you can make it happen again, note the date and time (PC clock time) and if it does eventually load, make a diagnostics log immediately after that. If it crashes, make a log immediately after restarting, and note that when you send the log.

It looks like it crashes silently. It already happened twice, but when I create diagnostic logs, there are no new records in crash_archive, and nothing in other logs that suggests any errors, or looks different from the logs I already sent you. Are there any other diagnostic methods?

UPD: looks like it's a well-known issue, and following the advice in the 2-year-old thread helped me. It's quite odd that nothing has been done about that since 2023.

panos_mts wrote:The temporary freeze is a known issue and is related to the number of render jobs in the database. The more render jobs you have across all projects, the longer the delay when opening the Deliver tab for the first time. A workaround is to delete the render jobs from all projects. It's unclear why this hasn't been fixed after two years.

Here is a related thread
viewtopic.php?f=21&t=184019

That's an absolute disgrace.

Thank you. I followed the advice in that thread, and the problem is resolved, at least for now. No more freezes when switching to the delivery page, and no more crashes.