Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Process.Kill(true) instead of KillTree #15821

Merged
merged 1 commit into from
Feb 12, 2021
Merged

Conversation

pranavkm
Copy link
Contributor

No description provided.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@pranavkm pranavkm added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label Feb 11, 2021
@pranavkm pranavkm marked this pull request as ready for review February 11, 2021 23:31
@pranavkm
Copy link
Contributor Author

I'm going to yolo this for 6.0. We can see what falls out of it.

Copy link
Contributor

@jkotalik jkotalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure you follow up on this for the runtime folks!

Also, we want to do the same on the aspnetcore repo.

@danmoseley
Copy link
Member

linking dotnet/runtime#45017

@pranavkm
Copy link
Contributor Author

@danmoseley I tried this change in the ASP.NET Core repo: dotnet/aspnetcore#29016 but had to cancel that PR because the change caused some tests (that attempt to process-kill) to hang indefinitely. dotnet-watch has tests that verify the process it launches is killed, but none that verifies that a graph of processes is cleaned up. But preview2 is as good as any release to get customer feeedback on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants