phoeniximagery wrote:Hi Dwaine,
I think we've spoken in the past regarding GPU issues, however, I now have this same issue and it is not the dynamic ports issue as the behavior is different. fscript.exe launches a number of instances and connects to local host, then after several seconds, each pair of instances closes.
But there's no longer any attempts to connect to anything.
I have no software firewall.
Your above comments regarding OpenCL are a dead end as well. Resolve worked fine with the previous version I had in 20H1 v2.2.5.0. In my case, I'm running Windows 10 version 2004, build 20150.1000 as above which ships with OpenCL v2.2.8.0. So what you're saying about OpenCL doesn't add up exactly. But I digress.
So I'm with you in thinking there's something screwy with this latest update. But I haven't ascertained what it is just yet but I'm working on it. I will say though that resolve.exe DOES go into not-responding and the wait state indicates that it's awaiting a network I/O to complete. JUST like the issues caused by the dynamic ports issue. And AFTER all the fscript.exe instances close, there is no longer any process listening on tcp-udp/1144.
I can say with confidence that this is not a Hyper-V issue, a docker issue, it's not a GPU driver issue, it's not a sticky mouse button, or mice chewing on my power supply wires. It's an incompatibility with either DPDecoder.exe, Resolve.exe, fscript.exe or one of their external required libraries that has a dependency on an OS library for which an exception handler was not written into the resolve source code as it must have been assumed that whatever method or function it's looking for in that OS library would always be there for all time.
I'll continue testing and collecting data and I'll report back and see if we can't get to the bottom of this jabberwocky.
Thank you for attending my TED Talk.
Great summation. Totally agreed.
I do wonder what information do the Capture logs provide to the developers. The problem/error should be obvious (or not!!??)
@Dwaine, I am anxiously waiting for the next windows build to come in this week. I was hoping to get some good news from you though. I have been going through the forum and the Fairlight issue spans almost a decade. Various OS's, various versions of DaVinci etc. Various users coming up with various remedies and some of them resolving it! Logically it certainly seems it goes beyond just the fact that I have an insider preview build installed.
What do these lines mean.......(socket failed to connect to server, error: 10061)
[0x0000206c] | SyManager | WARN | 2020-06-23 14:31:09,164 | socket failed to connect to server, error: 10061
[0x0000206c] | SyManager | ERROR | 2020-06-23 14:31:09,164 | DRIVER: panel connection failed
[0x00001c70] | Fairlight | INFO | 2020-06-23 14:31:15,355 | 00.00.06.934(001): Running Fairlight (r000775-55722853)
Thanks again for your patience and your kindness.
Cheers
Max