Debug Session Crashing
See original GitHub issueSystem Details
System Details Output
PS C:\Users\admin> & {"### VSCode version: $(code -v)"; "`n### VSCode extensions:`n$(code --list-extensions --show-versions | Out-String)"; "`n### PSES version: $($pseditor.EditorServicesVersion)"; "`n### PowerShell version:`n$($PSVersionTable | Out-String)"}
>>
### VSCode version: 1.53.2 622cb03f7e070a9670c94bae1a45d78d7181fbd4 x64
### VSCode extensions:
ms-mssql.mssql@1.10.1
ms-vscode-remote.remote-wsl@0.53.4
ms-vscode.powershell@2020.6.0
ms-vscode.powershell-preview@2021.2.1
### PSES version: 2.3.0.0
### PowerShell version:
Name Value
---- -----
PSVersion 7.1.2
PSEdition Core
GitCommitId 7.1.2
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Issue Description
While debugging my PowerShell script. I am occasionally witnessing a crash, even without breakpoints.
The terminal process "C:\Program Files\PowerShell\7\pwsh.exe '-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Bypass', '-Command', 'Import-Module 'c:\Users\Admin\.vscode\extensions\ms-vscode.powershell-preview-2020.9.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.9.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users\Admin\.vscode\extensions\ms-vscode.powershell-preview-2020.9.0\modules' -EnableConsoleRepl -StartupBanner '=====> PowerShell Preview Integrated Console v2020.9.0 <=====
' -LogLevel 'Normal' -LogPath 'c:\Users\Admin\.vscode\extensions\ms-vscode.powershell-preview-2020.9.0\logs\1614183831-e2d954c4-63bd-4c5c-af23-38fe0cbdf90c1613690344185\EditorServices.log' -SessionDetailsPath 'c:\Users\Admin\.vscode\extensions\ms-vscode.powershell-preview-2020.9.0\sessions\PSES-VSCode-15944-887475' -FeatureFlags @() '" terminated with exit code: 3762504530.
Expected Behaviour
Code should run all the way through without crashing the PowerShell terminal window.
Actual Behaviour
I receive the error above & have to restart the PowerShell extension in VSCode.
Attached Logs
Follow the instructions in the troubleshooting docs about capturing and sending logs.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
VS2019 is crashing during start of the debug session if ...
Developer Community. VS2019 is crashing during start of the debug session if "Enable Edit and Continue" is switched off.
Read more >Quick Fix: Visual Studio 2019 Debugger Crashing When ...
When attempting to debug X++ code the Visual Studio 2019 debugger can crash unexpectedly, which can be rather frustrating. Microsoft is aware of ......
Read more >Debugging with active breakpoint crashes Powershell session
Powershell session crashes in preview extension when attempting to debug a script with active breakpoint in unsaved file.
Read more >Acquiring crash reports and diagnostic logs - Apple Developer
If you'd like to gather the full crash report for the issue, detach the debugger, either by using the Debug > Detach menu...
Read more >Debug IOS Crashes Efficiently With Datadog RUM
The session timeline charts all the view loads, errors, and user actions that occurred during the relevant session that produced the crash.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@andschwa I’ve followed your instructions. Will report back if i’m still getting errors during debugging. @SydneyhSmith I’m using neither to my knowledge. Also, I no longer have untitled15.ps1 in my active code window.
This issue is being closed as inactive, if this issue is still occurring it will be re-opened