Resolve Takes Forever to Load- "Loading Projects" For 10 min

For a while now, I'm having an issue where Resolve takes a LONG time to start. It's getting progressively worse which is why I hadn't posted until now. When I start it up, it gets through all the steps on the splash screen until it gets to "Loading Projects" and then works on that for a long time - 5-10 minutes often. I'm using a network project library.

In Activity Monitor, the process is using around 200% CPU (in another system monitor app I have, iStat, it shows 20% of total CPU usage is Resolve, and since I have 10 cores it sounds like two cores are just spinning at 100% for a while). The process stays at about 1.5GB memory usage during this time.

Has anyone seen an issue like this? Any suggestions?

EDITED AS I TROUBLESHOOT:
Things I've tried that haven't had any (noticeable) effect:
- Optimizing the database/project library
- Creating a new network database and copying a project to it then restarting while in that database
- Restarting Resolve/computer
- Opening Resolve with each different page having been open when the app was last closed
- On the Deliver page, switched to seeing queued render jobs from all projects in the project library, cleared all jobs
- In Resolve Preferences - User - UI Settings, disable "Reload last working project on start up"
- in Preferences - User - Project Save and Load, disable "Load all timelines when opening projects"

You don't mention what system you're on, but when I had a number of USB connected drives and card readers connected to the system, some of which had shut down to sleep mode due to non-access in a while, Resolve would take a Long time to load as the OS seemed to wake each drive individually and wait for it to spin up and respond. Same with any network drives that might not be active and accessible.

This was on a current Win 11 system.

Might be worth disconnecting those that you can and see if that changes things.

Good luck.

You don't mention what system you're on, but when I had a number of USB connected drives and card readers connected to the system, some of which had shut down to sleep mode due to non-access in a while, Resolve would take a Long time to load as the OS seemed to wake each drive individually and wait for it to spin up and respond. Same with any network drives that might not be active and accessible.

This was on a current Win 11 system.

Might be worth disconnecting those that you can and see if that changes things.

Good luck.

Thanks for the reply! Just tried opening Resolve with only power connected, same result sadly. I'm on a Mac and the rest of my specs are in my signature.

[Dwaine Maggart]

Couple of things:

If you have network project libraries that are not available, it can take 90 seconds for trying to access each of those before it times out and moves to the next.

People have reported that if you have lots of old render projects listed in the Deliver page render queue, that can cause a delay switching to the Deliver page. If you happen to exit Resolve on the Deliver page, next time you launch Resolve, it will open on the Deliver page, and those same render queue items will delay the launch. On the Deliver page, select the 3 dot menu in the upper right of the Render Queue window, and select Show All Projects. If there is lots of stuff there, you may want to use the Clear Rendered or Clear All menus to speed things up.

If you have network project libraries that are not available, it can take 90 seconds for trying to access each of those before it times out and moves to the next.

Good to know! I should have been more specific- I'm using "network" libraries but they're all running off my computer internally as the server, so they shouldn't be affected by network speed if I'm understanding the underlying architecture correctly.

People have reported that if you have lots of old render projects listed in the Deliver page render queue, that can cause a delay switching to the Deliver page. If you happen to exit Resolve on the Deliver page, next time you launch Resolve, it will open on the Deliver page, and those same render queue items will delay the launch. On the Deliver page, select the 3 dot menu in the upper right of the Render Queue window, and select Show All Projects. If there is lots of stuff there, you may want to use the Clear Rendered or Clear All menus to speed things up.

The problem persists on any page that I open or close the app in. I just did what you said, and I did have a LOT of completed render jobs from all projects, so I cleared them all and restarted Resolve. Unfortunately this didn't seem to fix the problem, still a 10 minute launch.

Just bumping this thread in case anyone has any other ideas

[Dwaine Maggart]

A Resolve diagnostics log file, generated from the Resolve Help menu, could be helpful.

A Resolve diagnostics log file, generated from the Resolve Help menu, could be helpful.

Sure thing! The zip was too big to upload as an attachment to this message so I put it in Dropbox:
https://www.dropbox.com/scl/fi/l910xmjz ... m9lnw&dl=0

[Dwaine Maggart]

In Resolve Preferences - User - UI Settings, you have "Reload last working project on start up" selected.

And in Preferences - User - Project Save and Load, you have "Load all timelines when opening projects" selected.

Those 2 things in combination seem to be the issue.

I would recommend not having either of those options selected.

In Resolve Preferences - User - UI Settings, you have "Reload last working project on start up" selected.

And in Preferences - User - Project Save and Load, you have "Load all timelines when opening projects" selected.

Those 2 things in combination seem to be the issue.

I would recommend not having either of those options selected.

Oh that's interesting! I've been editing with both turned on for years and it never had this issue. I'll disable them and see what the result is and report back

In Resolve Preferences - User - UI Settings, you have "Reload last working project on start up" selected.

And in Preferences - User - Project Save and Load, you have "Load all timelines when opening projects" selected.

I would recommend not having either of those options selected.

Unfortunately this just transfers the problem to a different step. Instead of taking a long time during startup while "loading projects", it starts up in good time to the project manager. Then when I open a project, the app does nothing in the GUI for around 10 minutes before it finally opens the project. During this lag time, the process CPU usage hovers around 20% similar to what it did while "loading projects" during startup previously. Once Resolve has opened any single project, this delay goes away and I can open and close other projects in normal, fast times. But when I restart Resolve I have to wait the first time again.

I solved the problem and I have to admit, it was dumb user error

I've been learning Python and working on a lot of scripts for Resolve and also other tasks. I forgot that I put my git repository in the Resolve scripts folder, so on startup, Resolve was looking through every git subfolder/object/version before Resolve could load a project. This didn't affect performance initially but the more git saved versions the worse it got. Just did a file count and it had 50,000 files in there, largely because of git and the venv. Moved the repo out, and Resolve starts nice and fast. Oops!

[Dwaine Maggart]

Interesting. Thanks for the update! Could be helpful to others.

I put my git repository in the Resolve scripts folder, so on startup, Resolve was looking through every git subfolder/object/version


I laffed! But I will watch out for this when I finally dive into Resolve scripting because it seems like a natural thing to do.
Thanks for sharing.

[i]I laffed! But I will watch out for this when I finally dive into Resolve scripting because it seems like a natural thing to do.
Thanks for sharing.

Definitely watch out! Glad to help. Also feel free to reach out about scripting, I've gone pretty deep into it.