The VBScripts used by VAP are no longer able to terminate a COM QSF process (haven't tried AdScan yet).
The key code statements (excerpted) are:
set VideoReDo = VideoReDoSilent.VRDInterface
openFlag = VideoReDo.FileOpenBatch( args(1) )
outputXML = VideoReDo.FileSaveProfile(Args(2), Args(3))
When the operator stops (deliberately aborts) processing in VAP a file semaphore is written and detected by the VBScript, which causes it to execute the VideoReDo.Close().
This code stucture hasn't changed in months. But now, although the VBScript process terminates, the Videoredo exe process (per Task Mgr) just keeps on going until completion. And after completion a 25 MB chunk of the exe just sits on the process list using memory but no CPU cycles. To make things worse, when this rogue process generates the output file it displays the message box of statistics and plays the "i'm done" sound. I assume this must happen because the VRD process is missing its owner process (the VBScript).
I've been experimenting with this....I noticed the AbortOutput() COM function and found if I place that just before the Close() statement, at least the VRD process stops. However it still leaves a dead VRD process in task manager that is using memory but no CPU cycles.
Has the COM interface changed so as to trigger these problems?
Note: my platform is an i7 QuadCore running Win7 Pro 64bit and I've been using an H.264 output profile. I jumped from TVS4 build 610 to 618 then 619, so I don't know what version first had the problems.