blocks|key|1188506|text|一种方法是将父进程的PID传递给子进程。子进程将定期轮询具有指定pid的进程是否存在。如果不是，它就会退出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1188507|您还可以在子方法中使用Process.WaitForExit方法，以便在父进程结束时收到通知，但在任务管理器的情况下可能不起作用。|offset|length|1188508|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.diagnostics.process.waitforexit.aspx^0|0|B|J|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

One way is to pass PID of parent process to the child. The child will periodically poll if the process with the specified pid exists or not. If not it will just quit.

You can also use <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.process.waitforexit.aspx" rel="noreferrer">Process.WaitForExit</a> method in child method to be notified when the parent process ends but it might not work in case of Task Manager.

blocks|key|1188548|text|在进程开始后，调用job.AddProcess+better+to+do：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1188549|prc.Start();
job.AddProcess(prc.Handle);|code-block|syntax|javascript|1188550|在terminate之前调用AddProcess时，子进程不会被杀死。(Windows+7+SP1)|1188551|private+void+KillProcess(Process+proc)
{
++++var+job+=+new+Job();
++++job.AddProcess(proc.Handle);
++++job.Close();
}|1188552|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

call job.AddProcess better to do after start of the process:

<pre><code>prc.Start();
job.AddProcess(prc.Handle);
</code></pre>

When calling AddProcess before the terminate, child processes are not killed. (Windows 7 SP1)

<pre><code>private void KillProcess(Process proc)
{
 var job = new Job();
 job.AddProcess(proc.Handle);
 job.Close();
}
</code></pre>

blocks|key|1188600|text|我已经制作了一个子进程管理库，其中父进程和子进程通过双向WCF管道进行监控。如果子进程终止或父进程终止，都会通知对方。还有一个调试器帮助器，它可以自动将VS调试器附加到启动的子进程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1188601|项目网站：|1188602|http://www.crawler-lib.net/child-processes|offset|length|1188603|NuGet包：|1188604|https://www.nuget.org/packages/ChildProcesses+https://www.nuget.org/packages/ChildProcesses.VisualStudioDebug/|1188605|entityMap|0|LINK|mutability|MUTABLE|url|1|https://www.nuget.org/packages/ChildProcesses|2|https://www.nuget.org/packages/ChildProcesses.VisualStudioDebug/^0|0|0|0|16|0|0|0|0|19|1|1A|1S|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]|$F|17|G|18|1|19]]|A|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|E]]|S|$5|O|P|Q|A|$R|T]]|U|$5|O|P|Q|A|$R|V]]]]

I've made a child process management library where the parent process and the child process are monitored due a bidirectional WCF pipe. If either the child process terminates or the parent process terminates each other is notified.
There is also a debugger helper available which automatically attaches the VS debugger to the started child process

Project site:

<a href="http://www.crawler-lib.net/child-processes" rel="nofollow">http://www.crawler-lib.net/child-processes</a> 

NuGet Packages:

<a href="https://www.nuget.org/packages/ChildProcesses" rel="nofollow">https://www.nuget.org/packages/ChildProcesses</a>
<a href="https://www.nuget.org/packages/ChildProcesses.VisualStudioDebug/" rel="nofollow">https://www.nuget.org/packages/ChildProcesses.VisualStudioDebug/</a>

blocks|key|974507|text|我正在寻找一种不需要非托管代码的解决方案。我也无法使用标准的输入/输出重定向，因为它是一个Windows窗体应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|974508|我的解决方案是在父进程中创建一个命名管道，然后将子进程连接到同一管道。如果父进程退出，则管道中断，子进程可以检测到这一点。|974509|下面是使用两个控制台应用程序的示例：|974510|父级|974511|private+const+string+PipeName+=+"471450d6-70db-49dc-94af-09d3f3eba529";

public+static+void+Main(string[]+args)
{
++++Console.WriteLine("Main+program+running");

++++using+(NamedPipeServerStream+pipe+=+new+NamedPipeServerStream(PipeName,+PipeDirection.Out))
++++{
++++++++Process.Start("child.exe");

++++++++Console.WriteLine("Press+any+key+to+exit");
++++++++Console.ReadKey();
++++}
}|code-block|syntax|javascript|974512|孩子|974513|private+const+string+PipeName+=+"471450d6-70db-49dc-94af-09d3f3eba529";+//+same+as+parent

public+static+void+Main(string[]+args)
{
++++Console.WriteLine("Child+process+running");

++++using+(NamedPipeClientStream+pipe+=+new+NamedPipeClientStream(".",+PipeName,+PipeDirection.In))
++++{
++++++++pipe.Connect();
++++++++pipe.BeginRead(new+byte[1],+0,+1,+PipeBrokenCallback,+pipe);

++++++++Console.WriteLine("Press+any+key+to+exit");
++++++++Console.ReadKey();
++++}
}

private+static+void+PipeBrokenCallback(IAsyncResult+ar)
{
++++//+the+pipe+was+closed+(parent+process+died),+so+exit+the+child+process+too

++++try
++++{
++++++++NamedPipeClientStream+pipe+=+(NamedPipeClientStream)ar.AsyncState;
++++++++pipe.EndRead(ar);
++++}
++++catch+(IOException)+{+}

++++Environment.Exit(1);
}|974514|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I was looking for a solution to this problem that did not require unmanaged code. I was also not able to use standard input/output redirection because it was a Windows Forms application. 

My solution was to create a named pipe in the parent process and then connect the child process to the same pipe. If the parent process exits then the pipe becomes broken and the child can detect this.

Below is an example using two console applications:

<h2>Parent</h2>

<pre><code>private const string PipeName = "471450d6-70db-49dc-94af-09d3f3eba529";

public static void Main(string[] args)
{
 Console.WriteLine("Main program running");

 using (NamedPipeServerStream pipe = new NamedPipeServerStream(PipeName, PipeDirection.Out))
 {
 Process.Start("child.exe");

 Console.WriteLine("Press any key to exit");
 Console.ReadKey();
 }
}
</code></pre>

<h2>Child</h2>

<pre><code>private const string PipeName = "471450d6-70db-49dc-94af-09d3f3eba529"; // same as parent

public static void Main(string[] args)
{
 Console.WriteLine("Child process running");

 using (NamedPipeClientStream pipe = new NamedPipeClientStream(".", PipeName, PipeDirection.In))
 {
 pipe.Connect();
 pipe.BeginRead(new byte[1], 0, 1, PipeBrokenCallback, pipe);

 Console.WriteLine("Press any key to exit");
 Console.ReadKey();
 }
}

private static void PipeBrokenCallback(IAsyncResult ar)
{
 // the pipe was closed (parent process died), so exit the child process too

 try
 {
 NamedPipeClientStream pipe = (NamedPipeClientStream)ar.AsyncState;
 pipe.EndRead(ar);
 }
 catch (IOException) { }

 Environment.Exit(1);
}
</code></pre>

blocks|key|974539|text|只是我2018年的版本。在Main()方法之外使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|974540|++++using+System.Management;
++++using+System.Diagnostics;

++++...

++++//+Called+when+the+Main+Window+is+closed
++++protected+override+void+OnClosed(EventArgs+EventArgs)
++++{
++++++++string+query+=+"Select+*+From+Win32_Process+Where+ParentProcessId+=+"+%2B+Process.GetCurrentProcess().Id;
++++++++ManagementObjectSearcher+searcher+=+new+ManagementObjectSearcher(query);
++++++++ManagementObjectCollection+processList+=+searcher.Get();
++++++++foreach+(var+obj+in+processList)
++++++++{
++++++++++++object+data+=+obj.Properties["processid"].Value;
++++++++++++if+(data+!=+null)
++++++++++++{
++++++++++++++++//+retrieve+the+process
++++++++++++++++var+childId+=+Convert.ToInt32(data);
++++++++++++++++var+childProcess+=+Process.GetProcessById(childId);

++++++++++++++++//+ensure+the+current+process+is+still+live
++++++++++++++++if+(childProcess+!=+null)+childProcess.Kill();
++++++++++++}
++++++++}
++++++++Environment.Exit(0);
++++}|code-block|syntax|javascript|974541|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just my 2018 version.
Use it aside your Main() method.

<pre><code> using System.Management;
 using System.Diagnostics;

 ...

 // Called when the Main Window is closed
 protected override void OnClosed(EventArgs EventArgs)
 {
 string query = "Select * From Win32_Process Where ParentProcessId = " + Process.GetCurrentProcess().Id;
 ManagementObjectSearcher searcher = new ManagementObjectSearcher(query);
 ManagementObjectCollection processList = searcher.Get();
 foreach (var obj in processList)
 {
 object data = obj.Properties["processid"].Value;
 if (data != null)
 {
 // retrieve the process
 var childId = Convert.ToInt32(data);
 var childProcess = Process.GetProcessById(childId);

 // ensure the current process is still live
 if (childProcess != null) childProcess.Kill();
 }
 }
 Environment.Exit(0);
 }
</code></pre>

blocks|key|1188743|text|到目前为止提出的丰富的解决方案中又增加了一项……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1188744|他们中的许多人的问题是，他们依赖父进程和子进程以有序的方式关闭，当开发正在进行时，这并不总是正确的。我发现每当我在调试器中终止父进程时，我的子进程经常是孤立的，这要求我使用任务管理器杀死孤立的进程，以便重新构建我的解决方案。|1188745|解决方案是:在子进程的命令行中(或者在环境变量中传递侵入性更小的ID+)传递父进程ID。|1188746|在父进程中，进程ID如下所示：|1188747|Process.CurrentProcess().Id;|code-block|syntax|javascript|1188748|在子进程中：|1188749|Process+parentProcess+=+Process.GetProcessById(parentProcessId);
parentProcess.Exited+%2B=+(s,+e)+=>
{
++++//+clean+up+what+you+can.
++++this.Dispose();
++++//+maybe+log+an+error
++++....

++++//+And+terminate+with+prejudice!+
++++//(since+something+has+already+gone+terribly+wrong)
++++Process.GetCurrentProcess().Kill();
};|1188750|对于这在生产代码中是否可以接受，我有两个想法。一方面，这种情况永远不应该发生。但另一方面，这可能意味着重新启动进程和重新启动生产服务器之间的差异。而本不应该发生的事情往往会发生。|1188751|在调试有序关机问题时，它肯定是有用的。|1188752|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

Yet another addition to the abundant richness of solutions proposed so far....
The problem with many of them is that they rely upon the parent and child process to shut down in an orderly manner, which isn't always true when development is underway. I found that my child process was often being orphaned whenever I terminated the parent process in the debugger, which required me to kill the orphaned process(es) with Task Manager in order to rebuild my solution.
The solution: Pass the parent process ID in on the commandline (or even less invasive, in the environment variables) of the child process.
In the parent process, the process ID is available as:
<pre><code>Process.CurrentProcess().Id;
</code></pre>
In the child process:
<pre><code>Process parentProcess = Process.GetProcessById(parentProcessId);
parentProcess.Exited += (s, e) =&gt;
{
 // clean up what you can.
 this.Dispose();
 // maybe log an error
 ....

 // And terminate with prejudice! 
 //(since something has already gone terribly wrong)
 Process.GetCurrentProcess().Kill();
};
</code></pre>
I am of two minds as to whether this is acceptable practice in production code. On the one hand, this should never happen. But on the other hand, it may mean the difference between restarting a process, and rebooting a production server. And what should never happen often does.
And it sure is useful while debugging orderly shutdown problems.

blocks|key|1188775|text|对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1188776|创建流程时添加标签process.EnableRaisingEvents+=+true;|offset|length|style|CODE|1188777|csc+=+new+Process();
csc.StartInfo.UseShellExecute+=+false;
csc.StartInfo.CreateNoWindow+=+true;
csc.StartInfo.FileName+=+Path.Combine(HLib.path_dataFolder,+"csc.exe");
csc.StartInfo.WindowStyle+=+ProcessWindowStyle.Hidden;
csc.StartInfo.ErrorDialog+=+false;
csc.StartInfo.RedirectStandardInput+=+true;
csc.StartInfo.RedirectStandardOutput+=+true;
csc.EnableRaisingEvents+=+true;
csc.Start();|code-block|syntax|javascript|1188778|entityMap^0|0|9|Z|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Solution that worked for me:
When creating process add tag <code>process.EnableRaisingEvents = true;</code>:
<pre class="lang-cs prettyprint-override"><code>csc = new Process();
csc.StartInfo.UseShellExecute = false;
csc.StartInfo.CreateNoWindow = true;
csc.StartInfo.FileName = Path.Combine(HLib.path_dataFolder, &quot;csc.exe&quot;);
csc.StartInfo.WindowStyle = ProcessWindowStyle.Hidden;
csc.StartInfo.ErrorDialog = false;
csc.StartInfo.RedirectStandardInput = true;
csc.StartInfo.RedirectStandardOutput = true;
csc.EnableRaisingEvents = true;
csc.Start();
</code></pre>

blocks|key|974644|text|我也有同样的问题。我正在创建子进程，即使我的主应用程序崩溃，子进程也不会被终止。在调试时，我不得不手工销毁子进程。我发现没有必要让孩子在某种程度上依赖父母。在我的main中，我添加了一个try+catch，以便在退出时执行子进程的CleanUp()。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|974645|++++static+void+Main()
++++{
++++++++Application.EnableVisualStyles();
++++++++Application.SetCompatibleTextRenderingDefault(false);
++++++++try
++++++++{
++++++++++++Application.Run(new+frmMonitorSensors());
++++++++}
++++++++catch(Exception+ex)
++++++++{
++++++++++++CleanUp();
++++++++++++ErrorLogging.Add(ex.ToString());
++++++++}
++++}

++++static+private+void+CleanUp()
++++{
++++++++List<string>+processesToKill+=+new+List<string>()+{+"Process1",+"Process2"+};
++++++++foreach+(string+toKill+in+processesToKill)
++++++++{
++++++++++++Process[]+processes+=+Process.GetProcessesByName(toKill);
++++++++++++foreach+(Process+p+in+processes)
++++++++++++{
++++++++++++++++p.Kill();
++++++++++++}
++++++++}
++++}|code-block|syntax|javascript|974646|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had the same problem. I was creating child processes that never got killed if my main app crashed. I had to destroy manually child processes when debugging. I found that there was no need to make the children somewhat depend on parent. In my main, I added a try catch to do a CleanUp() of child processes on exit.
<pre><code> static void Main()
 {
 Application.EnableVisualStyles();
 Application.SetCompatibleTextRenderingDefault(false);
 try
 {
 Application.Run(new frmMonitorSensors());
 }
 catch(Exception ex)
 {
 CleanUp();
 ErrorLogging.Add(ex.ToString());
 }
 }

 static private void CleanUp()
 {
 List&lt;string&gt; processesToKill = new List&lt;string&gt;() { &quot;Process1&quot;, &quot;Process2&quot; };
 foreach (string toKill in processesToKill)
 {
 Process[] processes = Process.GetProcessesByName(toKill);
 foreach (Process p in processes)
 {
 p.Kill();
 }
 }
 }
</code></pre>

blocks|key|974683|text|如果你能捕捉到什么时候你的进程树应该被杀死，从.NET+5.0+(.NET+Core3.0)开始，你可以使用Process.Kill(bool+entireProcessTree)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|974684|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process.kill?view=netcore-3.1#System_Diagnostics_Process_Kill_System_Boolean_^0|1I|10|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you can catch situation, when your processes tree should be killed, since .NET 5.0 (.NET Core 3.0) you could use <a href="https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process.kill?view=netcore-3.1#System_Diagnostics_Process_Kill_System_Boolean_" rel="nofollow noreferrer">Process.Kill(bool entireProcessTree)</a>

I'm creating new processes using <code>System.Diagnostics.Process</code> class from my application. I want this processes to be killed when/if my application has crashed. But if I kill my application from Task Manager, child processes are not killed. Is there any way to make child processes dependent on parent process?

Kill child process when parent process is killed

服务器

调试器

Windows

我正在应用程序中使用System.Diagnostics.Process类创建新进程。当我的应用程序崩溃时，我希望这个进程被终止。但是如果我从任务管理器中杀死我的应用程序，子进程不会被杀死。有没有办法使子进程依赖于父进程？

问在父进程被终止时删除子进程
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在父进程被终止时删除子进程EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在父进程被终止时删除子进程
EN