-
Notifications
You must be signed in to change notification settings - Fork 523
Open
Labels
Issue-BugA bug to squash.A bug to squash.Needs: TriageMaintainer attention needed!Maintainer attention needed!
Description
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
Third debug of Powershell (with manually stop debug and source another ps1 file) cause connect etimedout
PowerShell Version
Name Value
---- -----
PSVersion 7.5.4
PSEdition Core
GitCommitId 7.5.4
OS Microsoft Windows 10.0.26200
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Name : ConsoleHost
Version : 7.5.4
InstanceId : b97c2998-5772-43c3-b18a-31653b2db7ee
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : zh-CN
CurrentUICulture : zh-CN
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspaceVisual Studio Code Version
PS> code --version
1.105.1
7d842fb85a0275a4a8e4d7e040d2625abbf7f084
x64Extension Version
PS> code --list-extensions --show-versions | Select-String powershell
[email protected]Steps to Reproduce
- In
C:\Users\<user_name>\Documents\PowerShell\Microsoft.VSCode_profile.ps1
. "C:\Users\<user_name>\Documents\PowerShell\Microsoft.PowerShell_profile.ps1"- In
C:\Users\<user_name>\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
function prompt {
Write-Host “===” # here has breakpoint
Write-Host ">" -NoNewline
return " "
}-
Add breakpoint (like screenshot below)
-
FIRST TIMEClickRunbutton on the right corner of VSCode and everything works fine, then clickStopbutton in the middle of debug panel. -
SECOND TIMEClickRunbutton then clickStopbutton, this time it takes longer for debug process to stop -
THIRD TIMEClickRunbutton, after sometime error comesconnect etimedout. And maybe result in high CPU usage.
any
run debugtry after that cause the same error unless restart VSCode
not sourcing another .ps1 in
Microsoft.VSCode_profile.ps1and debug, everthing works well.
Visuals
Logs
No response
Metadata
Metadata
Assignees
Labels
Issue-BugA bug to squash.A bug to squash.Needs: TriageMaintainer attention needed!Maintainer attention needed!