Hello, I am running visualCron version 6.1.2 and I find that when a job or task is timed out or if I click stop job on a job that runs a batch process, then any processes that batch process spawned are orphaned. Because visual cron kills only the task process and not the process tree for timeouts and other job terminations, there can be a buildup of orphaned processes on the server. Is this a known issue that has a fix in a later versions or perhaps planned for the future? Thanks.

For some reason, killing child processes, could affect stability on OS. We have not yet found why. Maybe we will make this part optional.

---

I see, on our production servers we use Process Explorer 
which has been very stable and predictable with killing process trees. Hopefully in the future the same sort of functionality for killing process trees can be integrated into the job/task termination processes in VisualCron?

For some reason, killing child processes, could affect stability on OS. We have not yet found why. Maybe we will make this part optional.

This is a really nice feature to have, instead of changing current functionality One can add Stop process tree as an option