PID Repeated in Endless Loop PowerShell Unresponsive

[moymike]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

I gave up on using VS-Code for Powershell because of this issue about about a month ago. I searched for a solution and found nothing. (and yes, I'm still using Powershell 5.1)

This morning I decided to bring up VScode to see any updates addressed the problem. No change, still looping PID. I did a bit more searching found this thread, which has since been closed. (#4191)

I am reopening this issue because it fully kills the Powershell extension, and the "solution" is buried in a closed thread which is tough to get a good search result on. This should be a hot button issue, fixed with an update. I am sure I am not the only one that found the extension fully blocked without recourse.

• Changing the setting "powershell.developer.editorServicesWaitForDebugger": true fixes the problem. I am not sure the "fixes" is the right term, maybe it just bypasses the problem.

• This same issue (on my box) persists on both the the current Powershell v2022.10.0 extension and the Powershell Preview v2022.10.1 extension. (I have one disabled, in case I have a problem with the other)

• After looping a good number of times, an error pops up on bottom right of VScode saying "Error loading webview: Could not register service workers: InvaliState Error. Failed to register a ServiceWorker: The document is in an invalid state."

• From this point, Killing the Terminal (Powershell Extension), gets you back to a simple Powershell terminal without the extension capabilities.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.19041.1682
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1682
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.72.2
d045a5eda657f4d7b676dedbfa7aab8207f8a075
x64

Extension Version

ms-vscode.powershell@2022.10.0
ms-vscode.powershell-preview@2022.10.1

Steps to Reproduce

Load a powershell script or launch VScode with a powershell script reloaded.

Visuals

No response

Logs

No response

[andyleejordan]

This is a developer setting, why do you have it set true if you're not using it?

[andyleejordan]

It gets weirder because the PSES build should not even be processing that code in release builds...something might be up with the pipelines.