VBP (64-bit) doesn't terminate at end of build

[jbenson]

This is strange. Last Friday I added a new final step to my build project, a "Kill Process" step with [Builder.ProcessID] as the value. Tested the step in the VBP designer - VBP terminated. Let the build run over the weekend and again this morning for good measure, just to be sure what I was seeing. Despite the attempt to kill the process, VisBuildCmd.exe always remains running in Task Manager (and Task Scheduler says the latest task is still running). Monday morning there was three instances of VisBuildCmd.exe running (Saturday, Sunday and Monday builds). I rebooted the VM Monday and now (Tuesday) one VisBuildCmd.exe is running under this morning's scheduled task.

I am officially out of ideas. What could be going on?

[kinook]

What does the build log show? Did the Kill Process step execute? You might instead try configuring the scheduled task to stop the task if it runs longer than, say, 8 hours.

[jbenson]

The log says the Kill Process step executed. That's the last line in the log.

I already have an option set in the scheduled task to stop the task after a certain number of hours. The task shuts down as intended but the VisBuildCmd.exe process remains in memory. You see why this is all so maddening?

[kinook]

I guess whatever is preventing the process from exiting normally is also preventing it from being terminated. You might try a Run Program step with a command of

taskkill /f /pid [Builder.ProcessID]

Can you ZIP and send your .bld file and build log file to support@kinook.com? It might give us some ideas for reproducing the problem you're experiencing. Thanks.