dotnet/runtime

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

已關閉

#85,383 建立於 2023年4月26日

在 GitHub 查看貢獻者指南
 (9 則留言) (0 個反應) (0 位負責人)C# (5,445 個分叉)batch import
area-System.Diagnostics.Processhelp wanted

倉庫指標

星標
 (17,886 顆星)
PR 合併指標
 (平均合併 12天 11小時) (30 天內合併 661 個 PR)

描述

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 ?

貢獻者指南

研究方向
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.
技術棧
csharp
領域
backend
議題類型
錯誤
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
半天
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
新近可參與
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
清晰
前置要求
C#Process management
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50