-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Closing integrated terminal causes window to crash with C++ assertion error #71789
Comments
(Experimental duplicate detection) |
Does this crash for you reliably? I haven't been able to reproduce at all personally. |
Can confirm this is now quite frequent. It may be associated with using the keybind to close the integrated terminal. I think it has happens when you go to close it after it has first launched up with the terminal already open. |
What's the build number of Windows 10? Is your repro just open and close the terminal? Could you also share your settings.json file? |
Windows 10 Home: 17134.706
The line |
Having the same issue, but only when my VScode workspace contains .ps1 sources. It is annoying, cause as long as the sources are part of the workspace the error is thrown when starting up VSCode. After removong the sources form the workspace VSCode can startup normally. Once VSCode opened normally the sources can be placed again in the workspace. VSCode version 1.33.1 |
I have the same issue as @lvanvugt I see that him and me are both NAV (Dynamics 365 Business Central) Partners, so I'm guessing he's using the same extensions as me the PowerShell guys already sent me here |
Now on VSCode 1.34.0 it's not bothering me anymore, even though the issue occured once. |
I'm also on VCode 1.30.0, but I've had the Problem 5 times today. |
This looks like an issue with our old terminal backend "winpty", going forward we are focusing our efforts on the new backend "conpty" which is build by the Console team at Microsoft and should fix many issues with the terminal under Windows. You can read more about getting ConPTY here. /duplicate #45693 |
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: "Shouldn't be affected by extensions"
Before window crashes this Microsoft Visual C++ Runtime Library error comes up.
The text was updated successfully, but these errors were encountered: