I have wrapped a custom application with winsw. My application creates child processes which then go on to create child processes of their own. When the windows service is stopped, some of the child processes get orphaned and thus cannot be stopped.

Steps to reproduce

1. Create an application that creates at least two levels of child processes below the main application.
2. Wrap said application with winsw
3. Install the service
4. Start the service
5. Wait for your two levels of child processes to spawn
6. Stop the service

Environment

• WinSW version: v3.0.0-alpha.11
• WinSW package type: x64
• Windows version: Server 2019
• Wrapped executable and version: internal project

Possible Solution

It appears winsw takes a top down approach to stopping the process tree. I believe a bottom up approach will solve the issue.

I have attached the appropriate logs for my issue.
myapp.wrapper.log