-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
continuous freezes and crashes on vscode extension (for the past ~1.5 weeks) #3216
Comments
@rjmholt let me know what you need for a repro or if I can turn up the logging or anything ? |
Thanks @brwilkinson is there any particular pattern to these crashes (like certain commands or projects?), also you mention that this has been the last 1.5 weeks-- were you seeing crashes before then just at a lesser frequency or was this a totally new issue for you? And similarly can you think of any environment changes that may have occurred when this started? Thanks for opening the issue it looks potentially related to PowerShell/PowerShellEditorServices#1295 |
I have mostly moved to just editing in Code, then executing scripts from the Windows Terminal to avoid the freezes, however I will do some work back in Code to see if I can get more logs etc. This is the latest freeze (from just now). symptons:
After it has hung, F8 shows these editor services logs.. however no output.
However the prompt never shows up in the terminal.This was the last crash/logs before it started the new log session.
VSCode extension seems fine, this was from when it started 10 mins ago. Since editor services crashed the last time.
other than that 1 restart for the extension, it was running since earlier today
$psversiontable
Name Value
---- -----
PSVersion 7.1.2
PSEdition Core
GitCommitId 7.1.2
OS Microsoft Windows 10.0.21318
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0 |
another one, this time I think it was the extension, not editor services ?! just executed an F8 and it crashed as below. not really much to show it started corrrectly then just shows the "3/3/2021 1:36:48 PM [NORMAL] - powershell.exe terminated or terminal UI was closed" 1:36.
|
not sure if they are helpful, however let me know what I can do to help. |
|
probably not related, however I have been getting this all day. . . just going to put it here, since we don't have anything much to go on for the above crashes. code with powershell extensions Also on a brand new lab machine vm that I just deployed fresh. (code with powershell extensions) Windows Powershell and Powershell 7.1.2 looks like this one is related to #2377 However the original crashes above are still occuring. |
I switched back to Preview extension this morning. my current theory is that this setting has resolved this issue: "terminal.integrated.enablePersistentSessions": false will update in another 12 hours. |
@SydneyhSmith so I have done quite a bit of testing in 12 hours blocks. it does appear that disabling this makes this issue disappear. I tested across 3 different machines, including freshly deployed machines with minimal other configs on them. "terminal.integrated.enablePersistentSessions": false This crash:
|
Just FYI the Preview and Stable extensions currently have the same code. |
Ah ha! @brwilkinson I think you might be experiencing a different face of the VS Code bug introduced in 1.53, and discussed in #3227. Could you try updating to 1.54.2 and set that setting back to |
thanks @andschwa will keep you posted. |
Issue Description
continuous freezes and crashes on vscode extension (for the past ~1.5 weeks)
either crashes similar to below:
or the console simply stops showing output during a long running command, such as a deployment.
It just cycles on this error and never returns in the console, until it's reset.
Attached Logs
Follow the instructions in the README about
capturing and sending logs.
Environment Information
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: