VidCoder
VidCoder copied to clipboard
RandomEngy
VidCoder reported job Failed, but encoding then Succeeded
Problem Description
OS Name Microsoft Windows 10 Pro, Version 10.0.19045 Build 19045
Rare bug: I've seen it before, but not for a long time. VidCoder reported Failed, but when I tried to clean up the output file, it was still in use. I then checked Task Manager, and found that VidCoder Worker was still running. I waited, and the job completed, except the output filename still had "part" appended. Logs are attached.
What version of VidCoder are you running?
11.9
Encode Log
I've been dealing with failed encodes as of late. Trying many things like not doing 4 simultaneous encodes and even downgrading to version 9 Sometimes I get a working file I can still play even though it says failed but it has the "part" in the name which I correct. Other times I cant play the file.
I'm just doing one encode at a time. Here's why: On my relatively ancient Skylake (quad core) CPU:
- 1 encode: 25.29 fps
- 2 simultaneous encodes: 25.72 (12.86 + 12.86) The difference is negligible.
Has this kind of error returned since you switched to a new computer? That would be really interesting to learn, if you've been having the same workload but a different Windows install fixed it.
What might be going on is that the interprocess communication pipe was just getting corrupted. I didn't know if it was my fault or the system's fault, and checked the pipe communication thread locks several times. But if you're in the clear now, I'm suspicious that some Windows install configuration or driver may be at fault here.
If others keep reporting it, I may have to just set up a reconnection attempt.
On my newish computer running Windows 11 Pro I've not seen this particular error. The only error I've seen is the one I reported in #1276 and just that one time.