dotnet/runtime

Kill(entireProcessTree: true) - cannot terminate self (?)

Closed

#85,383 opened on Apr 26, 2023

View on GitHubContributor guide
 (9 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-System.Diagnostics.Processhelp wanted

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

This works as expected and terminates application : Process.GetCurrentProcess().Kill(entireProcessTree: false);

This throws InvalidOperation Process.GetCurrentProcess().Kill(entireProcessTree: true);

Exception origin here ; https://github.com/dotnet/runtime/blob/10438a57b888cbdc6dc15771dc662adde9fd6b14/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.NonUap.cs#L25

image

**

Would it be possible to allow also the 'self-termination-with-children' scenario gracefully ?

Contributor guide

Research direction
Examine the file src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.NonUap.cs around line 25 to understand why Kill(entireProcessTree: true) throws InvalidOperationException for the current process. Look at the existing logic that checks for self kill and consider modifying it to allow self termination with children. Review any comments in the issue or related discussions for potential pitfalls. Implement a fix that handles this edge case gracefully, ensuring it doesn't break existing behavior.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Process management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50