Static methods in PSClasses are sometimes marshaled to disposed runspaces

logs.zip
ReproSteps.zip

Steps to reproduce

1. Download an extract in the included example.

2. Move the folder "Example" into your PSModulePath

3. Open the folder "Example2" in VSCode

4. Open the file "First.ps1" and run the command Test-Class (this is a function from "Example")

5. (Optional) Run the command included in "First.ps1", this will show the runspace the static method is currently bound to.

6. Open the file "Second.ps1" and run the command Test-Class again.

7. (Optional) Run Get-BoundRunspace again.

Expected results

The command Test-Class to output Test was successful both times, and Get-BoundRunspace to return the current default runspace both times.

Actual results

The command Test-Class works the first time, but after the second file is opened it throws a null reference exception and Get-BoundRunspace shows a runspace that is no longer open.

Notes

The steps are exact, if Test-Class isn't ran before switching files, or if "Second.ps1" is loaded first, it won't happen.

Although the steps may seem strange, this happens to me frequently if my module is in the module path, and makes static methods in classes not viable. My assumption is that PSES creates a runspace for PSSA which then loads the module causing that execution context to be the new owner. The runspace is then disposed, but the owner doesn't revert.

Beginnen Sie mit ReproSteps.zip und logs.zip und folgen Sie anschließend den aufgelisteten Schritten für Test-Class und Get-BoundRunspace, während Sie den Runspace-Besitz statischer Methoden über First.ps1 und Second.ps1 hinweg nachverfolgen. Als abgeschlossen gilt die Aufgabe, wenn der Befehl bei beiden Läufen erfolgreich ist und Get-BoundRunspace den aktuellen Standard-Runspace statt eines verworfenen meldet.