在进程终止之前未能关闭/处置 Powershell Runspace 对象会产生什么影响？
假设应用程序在应用程序的生命周期内维护 Runspace 对象（来自 System.Management.Automation.Runspaces）的单例实例，那么在应用程序终止之前未能释放 Runspace 会产生哪些潜在副作用？
我所了解的设计原理是，在这种情况下，内存/句柄泄漏不是问题，因为进程终止会强制释放所有这些资源，并且单例具有与应用程序相同的生命周期。该设计是否还忽略了其他考虑因素？
Given an application that maintains a singleton instance of a Runspace object (from System.Management.Automation.Runspaces) for the lifetime of the application, what are the potential side effects of failing to dispose of the Runspace before the application is terminated?
The design rationale I have been presented with is that memory/handle leaks are a non-issue in this case because the process termination forces all of those resources to be freed anyway, and the singleton has the same lifetime as the application. Are there other considerations that are ignored by that design?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我的理解和你的一样 - 由于 PowerShell 是托管代码，因此 .NET 框架应该在你退出后进行清理。
My understanding is as yours - since PowerShell is managed code, the.NET framework should clean up after you quit.