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

Integrated Terminal not loading #37044

Closed
willielee opened this issue Oct 27, 2017 · 8 comments
Closed

Integrated Terminal not loading #37044

willielee opened this issue Oct 27, 2017 · 8 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label windows VS Code on Windows issues
Milestone

Comments

@willielee
Copy link

  • VSCode Version: Code 1.17.2 (b813d12, 2017-10-16T13:59:46.104Z)
  • OS Version: Windows_NT x64 10.0.14393
  • Extensions: none

Steps to Reproduce:

  1. Ctrl + ` (to start Integrated Terminal)

When starting Integrated Terminal, prompt never appears.

Errors in Developer Tools Console:

[Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking
event handler as 'passive' to make the page more responsive.
C:\Program Files\Microsoft VS Code\resources\app\node_modules\xterm\lib\Terminal.js:1379 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
C:\Program Files\Microsoft VS Code\resources\app\node_modules\xterm\lib\Terminal.js:1379 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
scorer.ts:133 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.

vscodeintegratedtermina3

Attempts at correcting issue:

  1. Reinstalled VS Code (most recent and Insiders)
    • including deleting $HOME\AppData\Roaming\Code
  2. Resizing pane/window (this is not a duplicate of terminal not painting until resize #34554)
@vscodebot vscodebot bot added the api label Oct 27, 2017
@dbaeumer dbaeumer added terminal General terminal issues that don't fall under another label and removed api labels Oct 30, 2017
@Tyriar
Copy link
Member

Tyriar commented Oct 30, 2017

@willielee what's your shell set as in your settings? This happens when a sysnative path is used on a 64-bit machine instead of a system32 path.

@Tyriar Tyriar added the info-needed Issue requires more information from poster label Oct 30, 2017
@teom10
Copy link

teom10 commented Oct 30, 2017

I have the same issue :(

@willielee
Copy link
Author

willielee commented Oct 31, 2017

@Tyriar

Settings:

"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",

Also tried:

  1. Copied and pasted that into Run and Powershell opens.
  2. Edited User Settings to use bash (Git Bash), same result, terminal does not load.
  3. Also able to run Git Bash.

vscodeintegratedterminal3

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Nov 2, 2017
@Tyriar Tyriar added this to the Backlog milestone Nov 2, 2017
@Tyriar
Copy link
Member

Tyriar commented Nov 2, 2017

I've seen a few reports of these and they seem to all be on Windows. From my knowledge there are a few ways that you can get into this status:

  • You're using an invalid path as your shell, a common example of this is using sysnative over system32 when on 64-bit Windows and the 64-bit VS Code client
  • The shell crashes immediately (related to the first point)

@Tyriar Tyriar added the windows VS Code on Windows issues label Nov 2, 2017
@jky7
Copy link

jky7 commented Nov 7, 2017

I'm experiencing the same issue, I get this message as well when it tries to open the terminal

"The terminal process terminated with exit code: 3221225794"

this happens regardless of what terminal I use, tried powershell, cmd, ubuntu

@pexxi
Copy link

pexxi commented Feb 13, 2018

Similar issue in Mac too.
Terminal stays blank, but can be restored by switching to a different tab and then back to terminal tab.
This seems to happen especially after Mac is waking up from sleep.

@Tyriar
Copy link
Member

Tyriar commented Feb 13, 2018

@pexxi I think that's a different problem, caused by Chromium losing/corrupting the texture after sleeping (it can also happen in the minimap).

@Tyriar
Copy link
Member

Tyriar commented Feb 13, 2018

Duplicate #43169 (comment)

@Tyriar Tyriar closed this as completed Feb 13, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 13, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) 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

6 participants