Skip to content
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

Closed
kaleidawave opened this issue Apr 5, 2019 · 11 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label windows VS Code on Windows issues
Milestone

Comments

@kaleidawave
Copy link

  • VSCode Version: 1.33.0
  • OS Version: Win10

Steps to Reproduce:

  1. Closing the integrated terminal

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.

image

@vscodebot
Copy link

vscodebot bot commented Apr 5, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@Tyriar
Copy link
Member

Tyriar commented Apr 12, 2019

Does this crash for you reliably? I haven't been able to reproduce at all personally.

@Tyriar Tyriar added freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues terminal General terminal issues that don't fall under another label info-needed Issue requires more information from poster windows VS Code on Windows issues labels Apr 12, 2019
@Tyriar Tyriar added this to the Backlog milestone Apr 12, 2019
@kaleidawave
Copy link
Author

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.

@Tyriar
Copy link
Member

Tyriar commented Apr 14, 2019

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?

@kaleidawave
Copy link
Author

Windows 10 Home: 17134.706
So yeah it seems to crash if you close the terminal from when it first launched up.

{
    "window.zoomLevel": 0,
    "git.ignoreMissingGitWarning": true,
    "breadcrumbs.enabled": true,
    "workbench.sideBar.location": "right",
    "html.format.wrapLineLength": 0,
    "window.restoreWindows": "all",
    "workbench.startupEditor": "none",
    "editor.minimap.enabled": false,
    "search.usePCRE2": true,
    "csharp.referencesCodeLens.enabled": false,
    "explorer.confirmDragAndDrop": false,
    "git.enableSmartCommit": true,
    "explorer.confirmDelete": false,
    "terminal.integrated.shell.windows": "C:\\windows\\System32\\cmd.exe",
    "git.confirmSync": false,
    "terminal.integrated.rendererType": "dom",
    "javascript.suggest.completeFunctionCalls": true,
    "editor.autoClosingBrackets": "beforeWhitespace",
    "javascript.updateImportsOnFileMove.enabled": "always",
    "git.autorefresh": false,
    "terminal.integrated.cursorStyle": "line",
    "terminal.integrated.windowsEnableConpty": false,
    "workbench.iconTheme": "material-icon-theme"
}

The line terminal.integrated.windowsEnableConpty": false, was added after the crashes appeared from a thread on a similar issue but has not affected the random crashes. This has only happened recently (~last 3 weeks)

@lvanvugt
Copy link

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

@JulianTillmann
Copy link

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

@JulianTillmann
Copy link

By the way, the insiders version has the same issue
image

@lvanvugt
Copy link

Now on VSCode 1.34.0 it's not bothering me anymore, even though the issue occured once.

@JulianTillmann
Copy link

I'm also on VCode 1.30.0, but I've had the Problem 5 times today.

@Tyriar
Copy link
Member

Tyriar commented Oct 9, 2019

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

@Tyriar Tyriar closed this as completed Oct 9, 2019
@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 9, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

4 participants