VidCoder reported job Failed, but encoding then Succeeded

[JNavas2]

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.

[Logs.zip](https://github.com/user-attachments/files/18483164/Logs.zip)

What version of VidCoder are you running?

11.9

Encode Log

[YaBoyJon23]

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.

[JNavas2]

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.