Resolve gets stuck at program manager for 3-4 minutes

I have been using Resolve(free) from v15 but never had a problem like this which is happening since 17.2 update and also in 17.2.1. From opening to the program manager is very fast, but then it gets stuck for a few minutes, nothing happens on clicking a project. The default empty project takes 3-4 minutes to open.

Have done the usual -clean install of nvidia driver, tried older versions of the driver, clean install of Resolve, turned off anti-virus, etc.

No such issue in 17.1.1 on the same hardware.

It's quite frustrating.

Can't post link to or attach log file as it throws up message of "you are not allowed to post url" and "this extension is not allowed."

Can't post link to or attach log file as it throws up message of "you are not allowed to post url" and "this extension is not allowed."

Just put a space in the link so the system doesn't recognise it as a URL.

Also, if you're on Windows, I suggest you run System Information and do a File->Save and include that.

Log file-

wwwDOTdropboxDOTcom s xtxp0hivzgoeyxe davinci_resolve%20-%20Copy.log?dl=0

Replace space with slash

Do you have any USB devices attached besides keyboard and mouse?

Log file-

wwwDOTdropboxDOTcom s xtxp0hivzgoeyxe davinci_resolve%20-%20Copy.log?dl=0

Replace space with slash

Here's the unmangeled link for anyone else (hopefully from BMD)
https://www.dropbox.com/s/xtxp0hivzgoeyxe/davinci_resolve%20-%20Copy.log?dl=0

Robin, I've looked over the log and I see some places where there are long delays, but as to why is beyond me.

What Jim said is certainly worth trying. Some USB devices can cause problems with Resolve.

Another possibility is to try another graphics driver version.

Things I have on the usb are a keyboard, two mice and a TP-Link wifi adapter. I have tried removing all but a mouse, then all but the keyboard, restarting (just in case), changing ports -still the same problem.

The drivers I have tried are -471.11, 462.59 and 457.30, all studio versions. The last two worked just fine with Resolve 17.1.1. Any suggestions to which other to try or what else to do? I hope this gets fixed in the next update.

The drivers I have tried are -471.11, 462.59 and 457.30, all studio versions. The last two worked just fine with Resolve 17.1.1.

Perhaps try going back to 17.1.1 and see if the problem goes away. If it doesn't then that suggests something else has changed on your system. Perhaps a Windows update has broken something.

I hope this gets fixed in the next update.

Since many people are using 17.2.1 without the same problem it has to be something different with your system that's either broken or exposing a problem with Resolve.

What are your system specs?

[Shrinivas Ramani]

Given this is just one file from the log archive, there's not much that can be inferred, so these are a couple of starting diagnostic tests to check:

a. Is your Disk database on the local drive? Does it have a lot of projects? If you were to create a new database to check, do you see a difference?

b. There seems to be a lag when loading effects - if you have a lot of OpenFX or Fusion templates installed, backing them up and checking for startup time differences is worth a shot.

Again, this is the same analogy as "remove your USB devices and connect them back one at a time" - it helps narrow down what's causing the issue, so once that is determined you can put things back and plan workarounds.

Resolve 17.1.1 runs just fine. The problem started with 17.2 and continues in 17.2.1. I haven't checked if windows update broke something. Will try if possible.

All folders including database location are default on a local drive, a SSD.

To test I backed up and deleted all the projects I was working on, uninstalled all OpenFX plugins, even all audio VSTs, cleaned up the registry, and did a fresh install. The only projects now are the default empty one and a new empty one I created for testing. It's the same delay and freeze with both.

I have tried choosing GPU and CUDA manually in settings instead of auto. I think I have tried most suggestions found on the net.

Will post the whole log archive.

I have timed the delay and it is ALWAYS between 3 and 4 minutes, and nearly always about 3.15 to 3.30s. Here's an interesting observation: If I open Resolve but don't click on any project in the project manager and let it stand for, say, about 4 minutes, and then click on a project -it opens immediately!


It's as if there's something somewhere that stops the app for about 3 and a half minutes once program manager appears irrespective of anything.

It's rather curious.

Full log archive:
wwwDOTdropboxDOTcom s x41z9vxp914s4aq/DaVinci-Resolve-logs-_145844.rar?dl=0

Replace space with forward slash.

So I have been going through the log files and found this (this is from more than one log):

UI | INFO | 2021-06-25 14:33:36,895 | Launching project manager
UI | INFO | 2021-06-25 14:37:05,148 | Launching main window
Time difference: apprx 3m 29s




UI | INFO | 2021-06-25 14:45:37,003 | Launching project manager
UI | INFO | 2021-06-25 14:49:05,545 | Launching main window
Time difference: apprx 3m 29s




UI | INFO | 2021-06-25 14:55:02,295 | Launching project manager
UI | INFO | 2021-06-25 14:58:30,812 | Launching main window
Time difference: apprx 3m 29s




UI | INFO | 2021-06-25 14:33:36,895 | Launching project manager
UI | INFO | 2021-06-25 14:37:05,148 | Launching main window
Time difference: apprx 3m 29s




UI | INFO | 2021-06-25 14:45:37,003 | Launching project manager
UI | INFO | 2021-06-25 14:49:05,545 | Launching main window
Time difference: apprx 3m 29s



UI | INFO | 2021-06-25 14:55:02,295 | Launching project manager
UI | INFO | 2021-06-25 14:58:30,812 | Launching main window
Time difference: apprx 3m 29s

And so on.

The time from program manager UI appearing and main Resolve (project) window UI appearing is nearly exactly 3 minutes and 29s in EVERY case!

I don't know what to make of it.

Also I should mention the program manager UI isn't frozen, I can click the menus, right click works, I can expand the database sidebar. It's that program manager UI remains for 3 minutes and 29 seconds.

I appreciate all the answers, thanks!

I apologize for going on and on, but here's a video of the process with stopwatch for anyone interested- opening the default empty project:
https://www.dropbox.com/s/wl3zwjdp1010n7d/opening%20default%20project.wmv?dl=0

Heres's one of creating a new empty project:
[url]https://www.dropbox.com/s/d1crn0pgt0tnev3/creating%20new%20project.wmv?dl=0
[/url]

In both cases : 3 minutes and 29 seconds almost exactly!

I hope it helps squash some bugs in future.

You might try running Sysinternals Process Monitor. It will allow you to see what’s going on with Resolve while loading.

Years ago I used it to find why a certain version of Autocad was taking so long to load. Turned out it was trying to get a response from a nonexistent AWS IP address with a long wait time. I found a way to direct calls to that address to point to the localhost and it no longer waited for a response. Load time went from about a minute to 15 seconds.

There was recently an update of the NVIDIA studio driver - since this update the "waiting time" from the splash screen to the start of the project manager is again around 1 minute ... Resolve Studio Version 17.2.1

Hi Gary, thanks for the Systernals process monitor suggestion. I tired it and I can see Resolve spending a lot of time on some TCP Reconnect process.

Can you give details of how you solved the Autodesk problem, maybe that'll work here too?

[Dwaine Maggart]

Can you share a screen shot of that?

Screenshot of process monitor. I have both allowed and then blocked Resolve.exe in the firewall to see if it made any difference -none.

[Dwaine Maggart]

That looks pretty normal compared to my system. Which is 17.2.2 Studio. Here's what mine looks like. Started the monitor, then launched Resolve and selected the Untitled Project, which opened instantly.

I added TCP Connect to my filter and didn't select the Profiling. The 5432 ports are PostgreSQL accesses, and the 56xxx ports are collaboration ports.

resolve_process_monitor_2.png (283.13 KiB) Viewed 9637 times

If you could do another monitor run, with the same filters as I'm using, starting Resolve just after the monitor start, and then open the Untitled Project. After the project is opened, the process list should stop updating. Take the screen shot then.

Have you tried 17.2.2 yet? If not, try that and see if it behaves the same.

[Dwaine Maggart]

Basically, I don't think the 3 minute hang is related to TCP activity.

Create a new Disk database, and see if the issue persists in that.

The computer time for each process is noted in Process Monitor. Note the computer time when you start resolve and just leave it alone for 4 minutes. Note the computer time when the splash screen starts and when the project manager opens. Don’t open a project. After the 4 minutes stop Process Monitor. See what it is doing at and after those different times.

When the project manager starts and you just let it sit there for 4 minutes, is there a lot of disk activity? Windows Task Manager can also help with this.

And by the way, I can’t remember what I did to fix Autocad loading. I think I used some netsh commands.

Dwaine, screenshot of the Process Monitor just like you asked, from starting Resolve to the opening of the Untitled project.

I have tried making a new database, new empty project, and 17.2.2 -same delay.

I calculated the time taken by the TCP Reconnect-TCP Disconnect operation. It seems to basically run in sessions of about 21s and ran for a total of about 209s - or approx. 3 minutes and 29s. Same number as in my posts above.

See screenshot for one 21s session.

Dwaine, what’s the connection to port 1144 for? robinsmendez’s reconnect to port 1144 never receives data like yours did.

Here’s the link to the Autocad fix I posted on the Autocad forum. I don’t think it will work in this case though.

https://forums.autodesk.com/t5/installa ... -p/6341361

I'd just like to add you're not alone. I've been using Resolve since v12 and exactly the same thing has started happening to me since 17.2.x - frustratingly it's not every time, just nearly every time. And just when I think I've found what it is, I get the 3.5 minute wait the next time I load Resolve. 17.1 is fine, and I've changed nothing, so it has to be some change in Resolve - just that most people are not affected. I'll let you know if I find anything definitive...

Ian

Windows 10 x64, Asus X299v2, Intel Core i7 9th generation, 32GB RAM, Geforce 1070 8GB

So I had a fleeting success. I added the following text to the hosts file:

127.0.0.1 <computer name>:20321
127.0.0.1 <computer name>:1144

and then opened Resolve. From starting Resolve to opening the Untitled project: just 15 seconds or so! Utterly delightful. The Process Monitor looked as in the screenshot.

But then gave the PC a reboot and the same dreaded delay came back, sigh. I tried restoring the original hosts file and then adding the same text again inbetween reboots -but no. That one moment of thrill never reproduced again.

If this gives anyone a clue to the solution please let on, otherwise I'm resigned to waiting 3 minutes and 29 seconds every time Resolve opens.

Thanks everyone who tried to help.

[Dwaine Maggart]

Try these 2 things:

Open a PowerShell window in "Run as Administrator" mode and enter the following (copying the lines below and pasting them into the PowerShell window should work):

netsh int ipv4 set dynamicportrange protocol=tcp startport=49152 numberofports=16384

Run that. Did that help? If not, in the same PowerShell window, enter the following:

Get-NetTCPConnection | Where-Object { $_.State -eq "Listen" -and $_.LocalPort -eq 1144 } | ForEach-Object { (get-process -id $_.OwningProcess).Description }

Does it return any apps? Anything other than FusionScript services may be an issue.

To clarify, the second PowerShell command requires Resolve is already running.

[Dwaine Maggart]

No, not at all. Resolve does not need to be running for the second Powershell thing.

Okay, understood. I ran it without Resolve running and got zero results. Ran it with Resolve running and the output was Fusionscript service. Now I understand you were searching for other apps that might be set to listen on port 1144.

Dwaine, the first command worked! Resolve project opens real fast now. Thanks a ton, I'd never have have discovered the solution!

I have been plagued by this same issue since 17.2. The 'netsh' command also worked for my problem. Thanks Dwaine! I should add that this command does not work until after a system reboot.

I can't imagine that only three of us have been living with this issue, since 17.2. I hope this 'fix' gets well documented and available for the other users who might have missed this thread.

Dwaine, can you explain why this fix works, how it’s actually affecting Resolve, why the problem affected only some systems, and if the problem will be coded to be “bypassed” in future Resolve versions.

[Dwaine Maggart]

I have to thank Scott Brondel for this suggestion:

viewtopic.php?f=21&t=80763#p448407

As to how the systems default dynamic port range would be so changed, I have no idea. But this fix has helped a handful of people since he posted it in October 2018.

I'm wondering how these few systems got their dynamic port range changed? In the past (before Vista), the range included port 1144, but the default since Vista has been the higher range. I wonder if installing certain software meant for earlier OS's could have changed it?

Could the Resolve installer add a test and fix for this?

Check for dynamicportrange setting, if not the default, change it. If changed, throw up a "Reboot needed" message after the installer finishes.

[Peter Loveday]

Just wondering,

Do you happen to have Windows Hyper-V installed on the system(s) that showed this problem at all? Usually used by virtual machines or docker etc.

I am all of a sudden experiencing the same thing. Two days ago Resolve started fine and really fast. And now the Project Manager is stuck as well for quite some time.

I'll try the fix Dwaine mentioned, but I didn't do anything to either Resolve or my computer (as far as I know) and one day it worked, two days later. Not so much.

Sander, did you reboot your computer after applying the fix?

Hi Gary,

I did and it looks as though my issue is something different. It appears related to the project I'm opening.
I have one 2 hour+ project with about 90 cuts in it that takes about 3 minutes to open, but when I open another (smaller) project it opens within 5-10 seconds.

I don't think a relatively simple project should take this long to open, but it's - in hindsight - not the same issue.

[Peter Chamberlain]

We have an example project of 800 timelines and thousands of clips that does take some time to load but if its getting stuck then it might be an issue with the particular project, or a LUT (s0, plugin (s) OFX (s) and only reviewing the actual drp and repo the issue would give us any hope to see why.

[Peter Loveday]

I'm sure you already know this, Sander, but for others who might come across this... often long delays on Windows can be caused by network shares (possibly due to being referenced in a specific project, but seemingly not always) that have since gone offline.

We have an example project of 800 timelines and thousands of clips that does take some time to load but if its getting stuck then it might be an issue with the particular project, or a LUT (s0, plugin (s) OFX (s) and only reviewing the actual drp and repo the issue would give us any hope to see why.

I've exported the project that's giving me trouble. I'm not sure what 'repo the issue' means, so if there's something else you need, just let me know. Once opened the project works fine though.

https://www.dropbox.com/s/7yzt9419pn9vp ... t.drp?dl=0

I'm sure you already know this, Sander, but for others who might come across this... often long delays on Windows can be caused by network shares (possibly due to being referenced in a specific project, but seemingly not always) that have since gone offline.

I'm aware of this, but it's project that only has two video source files on a regular harddrive. It's a pretty big file (46 gb) but apart from that, there's nothing unusual about it.

Early days (because the problem occasionally didn't show) but the fix seems to be working for me. Thank you!
Ian

[Dwaine Maggart]

@Sander: This project loads quickly for me.

Is this the only project you are having an issue with? Opening a new project seems normal?

After loading the project, use the Resolve Help menu "Create Diagnostics Log on Desktop" to make a log file, and send that.

I'm sure you already know this, Sander, but for others who might come across this... often long delays on Windows can be caused by network shares (possibly due to being referenced in a specific project, but seemingly not always) that have since gone offline.

I'm aware of this, but it's project that only has two video source files on a regular harddrive. It's a pretty big file (46 gb) but apart from that, there's nothing unusual about it.

@Sanders are you using any 3rd party audio plugins? For me using noise reduction on a handful of audio files takes projects from opening in 10 seconds to several minutes even after trying caching and bouncing effects.

I was also seeing the same slow load issue. The netsh command also repaired mine.

I've had this problem sporadically for the last few months. This thread at least hinted that it will eventually startup. In the past I've always killed the Resolve process and sometimes rebooeted with inconsistent results.

I tried the netsh command, but that didn't help.

I did the 2nd command and didn't list any processes.

So now I just go drink coffee until Resolve finally starts up

Would still be nice to find the root cause and solution. This didn't used to be a problem on this system. Win10, Resolve 17.3.1. Some NAS storage that is mapped. I kind of remember this being a problem ever since Resolve 17. Never before going back many versions, and multiple systems. Nothing has dramatically changed.

Jan

Same problem even with 17.4.1. This is definitely a software problem, not a hardware problem because I have Resolve running on a 7GB/s NVMe (Sabrent Rocket 4 Plus 1TB) and my BRAW footage on a 5GB/s NVMe (Sabrent Rocket 4 1TB). Both the NVMe cards are running without a problem.

Resolve opens fast, no problem. Project Manager loads no problem. When I open a project I have to wait close to 5 minutes for the footage to load. Been having this problem since 17.3.