PowerShell extension v2022.6.1 is considerably slower than v2022.5.1 when debugging

[kborowinski]

Prerequisites

• I have written a descriptive issue title.
• I have searched all 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

PowerShell extension v2022.6.1 is considerably slower than v2022.5.1 when stepping through the code with F10 or F11.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.5
PSEdition                      Core
GitCommitId                    7.2.5
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0, 6.1.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
x64

Extension Version

ms-vscode.powershell@2022.6.1
TylerLeonhardt.vscode-inline-values-powershell@0.0.6

Steps to Reproduce

Update to v2022.6.1 and start debugging.

Visuals

v2022.6.1

vs

v2022.5.1

Logs

1655885189-747fa844-e7ea-41df-8507-281d6e9351021655885186880.zip

[andyleejordan]

PSES v3.4.0 is the first version bundled since the last stable. I'll go from there and see if I can identify the change which caused this.

[andyleejordan]

Bisected, first bad release seems to be v2022.5.2-preview. (Kris Borowinski (@kborowinski) where were you for the previews?! 😜)

[kborowinski]

Andy Jordan (@andschwa) Sorry 😅, didn't want to ruin your day. In my defense - I can't use preview versions of VSC or extensions at work. So there you have it 😋

[andyleejordan]

So, good news first, narrowed it down to PowerShell/PowerShellEditorServices#1799. Reverted that on top of master and everything was back to normal. Bad news: that's a big PR and we definitely want the functionality in it, so now we got some troubleshooting to do.