子进程:删除Windows中的子进程
在 Windows 上,subprocess.Popen.terminate
调用 win32 的 TerminalProcess
。 但是,我看到的行为是我尝试终止的进程的子进程仍在运行。 这是为什么? 如何确保该进程启动的所有子进程都被杀死?
On Windows, subprocess.Popen.terminate
calls win32's TerminalProcess
. However, the behavior I see is that child processes of the process I am trying to terminate are still running. Why is that? How do I ensure all child processes started by the process are killed?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
通过使用 psutil:
By using psutil:
将
taskkill
与/T
标志一起使用taskkill 的标志具有以下文档:
或者使用 comtypes 和 win32api 遍历进程树:
Use
taskkill
with the/T
flagThe flags to taskkill has the following docs:
Or walk the process tree using comtypes and win32api:
以下是 Job 对象方法的示例代码,但它使用
win32api.CreateProcess
而不是subprocess
Here's example code for the Job object method, but instead of
subprocess
it useswin32api.CreateProcess
这是一件很难做到的事情。 Windows 实际上并不在进程空间中存储进程树。 也不可能终止一个进程并指定它的子进程也应该死亡。
解决这个问题的一种方法是使用 taskkill 并告诉它破坏整棵树。
另一种方法(假设您正在生成顶级进程)是使用一个根据此类事情开发的模块:http://benjamin.smedbergs.us/blog/tag/killableprocess/
为了一般地为自己执行此操作,您必须花一些时间向后构建列表。 也就是说,一个进程存储指向其父进程的指针,但父进程似乎不存储有关子进程的信息。
因此,您必须查看系统中的所有进程(这实际上并不难),然后通过查看父进程字段手动将这些点连接起来。 然后,您选择您感兴趣的树并遍历整个树,依次杀死每个节点,一个接一个。
请注意,当父级死亡时,Windows 不会更新子级的父级指针,因此您的树中可能存在间隙。 我不知道你能对这些做些什么。
This is a hard thing to do. Windows does not actually store a process tree in the process space. Nor is it possible to terminate a process and specify that it's children should also die.
One way around that is to use taskkill and tell it to wack the whole tree.
Another way to do it (assuming that you are spawning the top-level process) is to use a module that was developed with this sort of thing in mind: http://benjamin.smedbergs.us/blog/tag/killableprocess/
In order to do this generically for yourself, you have to spend some time building the list backwards. That is, a process stores pointers to it's PARENT, but parents appear to not store information about children.
So you have to look at all the processes in the system (which really isn't that hard), and then manually connect the dots yourself by looking at the parent process field. Then, you select the tree you are interested in and walk the whole thing, killing each node in turn, one by one.
Note that Windows doesn't update a child's parent pointer when the parent dies, so there may be gaps in your tree. I'm not aware of anything you can do about those.
将子项放入 NT Job 对象,那么你就可以杀死所有的孩子
Put the children in a NT Job object, then you can kill all children
我遇到了同样的问题,只是通过 Windows 命令杀死进程,并选择杀死儿童“/T”
I had the same problem and just killing process via windows command with option for child killing "/T"
我使用 kevin-smyth 的答案为
subprocess.Popen 创建 直接替换
将创建的子进程限制在匿名作业对象中,设置为在关闭时终止:I used kevin-smyth's answer to create a drop-in replacement for
subprocess.Popen
that confines the created child process in an anonymous job object, set up for terminating on close:如果您像我一样从 vbs 脚本中创建一个对象,其逻辑类似于:
这是因为在 Windows 中,它会生成 excel 作为服务,并且它有所有者svchost.exe 而不是您的 VBS 脚本。 感谢发言人他们的回答对诊断这个问题非常有帮助。
我相当粗略地处理了这个问题,基本上在启动之前创建了一个 Excel 进程列表,然后获取另一个 Excel 进程列表并进行比较,新的 PID 是我的新 Excel 脚本。 然后如果我需要杀死它,我可以通过它的 PID 识别它来杀死它。
请注意,上述内容仅适用于我的特定情况,尽管我已尝试使其尽可能有针对性,但几乎肯定不应该在多线程环境中使用。
0.05s 的等待时间是根据经验发现的。 0.01s 太短了,0.03 有效,所以 0.05s 似乎是安全的。
except 块中的 else 只是一个包罗万象的工具,以防它无法记录创建了哪个 PID。 它将杀死自脚本启动以来作为服务启动的所有 Excel 进程。
更简洁的答案可能是扩展 Spokes 的链接答案并从 shell 内运行 excel,但我没有时间解决这个问题。
None of the answers will work if, like me, you're creating an Object from within your vbs script with logic similar to:
This is because in Windows this spawns excel as a service and it has the owner of svchost.exe rather than your VBS script. Thank you to spokes for their answer which was surpremely helpful in diagnosing this.
I went about this fairly crudely and basically created a list of excel processes before I start it, then get another list of the excel processes afterwards and compare them, with the new PID being my new excel script. Then if I need to kill it, I kill it by identifying it through its PID.
Note the above only works in my specific circumstance and even though I've tried to make it as targeted as possible it almost certainly should not be used in a multi-threaded environment.
The 0.05s wait was found empirically. 0.01s was too short, 0.03 worked, so 0.05s seemed safe.
The else in the except block is just a catch all in case it didn't manage to note which PID was created. It will kill all excel processes that have started as a service since the script began.
Neater answer is probably extending on Spokes' linked answer and running excel from within a shell, but I didn't have time to work through that.
您可以为此使用控制台进程组
subprocess
模块已提供必要的 Windows API:附加信息:
Windows进程创建标志
Python 子进程文档
Python 源代码示例
You can use Console process groups for this and the
subprocess
module already provides the necessary Windows API:Additional info:
Windows process creation flags
Python subprocess docs
Python source code example