fix: Kill browser process when 'taskkill' fails on Windows #8352
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
No, this PR affects windows only and affects how we shut down the browser process.
Summary
On windows, we use
taskkill
to kill the browser process. The reason is that we want to shutdown the whole process group, i.e. also kill all child processes spawned by the browser process. Callingtaskkill
can fail though, if its called by a user with not enough privileges, in that case we should fall back to usingsubprocess.kill
.As per Node.js documentation we also cleanup all the processes of a process group as long as we do not start the browser process in detached mode (which we do not do) once the main Node.js process dies.
Does this PR introduce a breaking change?
No
Other information
This might also fix issue #7922.