9b94f18ccf
The root cause is that `OutputBuffer` is not cleaned up (set to `null`) in `Stop` and `BeginStop/EndStop` when the powershell instance owns the `OutputBuffer` object. Since the pipeline has been intentionally stopped by the caller, the `OutputBuffer` should be set to `null` as well when it's owned by the PowerShell instance, just like how it's cleaned up in `EndInvoke`. |
||
---|---|---|
.. | ||
assets | ||
BasicEngine.Tests.ps1 | ||
GetNewClosure.Tests.ps1 | ||
InitialSessionState.Tests.ps1 | ||
LanguagePrimitive.Tests.ps1 | ||
ProxyCommand.Tests.ps1 | ||
Serialization.Tests.ps1 | ||
TypeInference.Tests.ps1 |