Performance is extremely slow while debbuging Powershell script after update to version 2022.6.1

[guilhermepriaxio]

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

Updated Powershell extension today and after the update the performance is extremely slow while debugging.

Reverted back to version [email protected] and the issue still persists, but is a little bit better then the last one;
Version [email protected] is a little bit better again but still very slow and with version [email protected] it run extremely fast.

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.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
x64

Extension Version

[email protected]

Steps to Reproduce

Open VsCode with a clean Wokspace;
Create a new file and paste the content bellow

function test{
    param ($a)
    write-host $a
}
test -a "test"

Powershell extension will load up.
Save the file;
Set a breakpoint at line 5 - test -a "test"
Start debbuging;
After hitting F5 to start the debug will actually start after a few seconds;
Step-into the function pressing F11 and again is very slow.

I'm just created this simple function to illustrate the problem the performance is slow with any code.

Visuals

No response

Logs

No response

[andyleejordan]

This was fixed in v2022.6.2-preview, closing as duplicate of #4038

[ghost]

This issue has been marked as duplicate and has not had any activity in a day. It has been closed for housekeeping purposes.