-
Notifications
You must be signed in to change notification settings - Fork 517
Closed
Labels
Area-UIBug: VS CodeBugs in VS Code itself.Bugs in VS Code itself.Issue-BugA bug to squash.A bug to squash.Needs: Author FeedbackPlease give us the requested feedback!Please give us the requested feedback!
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
Using Powershell extension in VSC to run and debug some scripts. Sometimes if there is some error in a script, the terminal will die or get frozen, and hitting F5 again starts doing weird things like giving odd errors or freezing. Once I realize what happened, I kill the powershell terminal window with the trash can icon. Only then does the panel close and reveal a pop-up that was hidden underneath it that seemed to have been hiding the whole time, saying "powershell has died would you like to restart it"
PowerShell Version
Name Value
---- -----
PSVersion 7.4.5
PSEdition Core
GitCommitId 7.4.5
OS Microsoft Windows 10.0.22621
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Name : Visual Studio Code Host
Version : 2024.4.0
InstanceId : db0853a3-35c7-4ac7-b616-9a2dbd6462cb
UI : System.Management.Automation.Internal.Host.InternalHostUserInte
rface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
1.95.3
f1a4fb101478ce6ec82fe9627c43efbf9e98c813
x64
Extension Version
ms-vscode.powershell@2024.4.0
Steps to Reproduce
- Open a terminal within VS Code
- Move the panel position to the right side
- make a script that is invalid or would cause an error
- Run it within VS Code editor with F5
- extension and terminal will freeze, not obvious what is happening
- close terminal with trash can icon
- now the error is visible that would have explained and recovered
Visuals
This should be shown, but is hidden by the terminal itself when the panel is on the right.
Logs
No response
Metadata
Metadata
Assignees
Labels
Area-UIBug: VS CodeBugs in VS Code itself.Bugs in VS Code itself.Issue-BugA bug to squash.A bug to squash.Needs: Author FeedbackPlease give us the requested feedback!Please give us the requested feedback!