vscode: when 2 vscode instance are open getting error "The connection to the terminal's pty host process is unresponsive, the terminals may stop working"

Issue Type: Bug

Hi,

I am using insiders build and have 2 workspaces ( 1 angular and other react), after a most recent update (24 Feb 2021, 10:20 IST) I am getting the mentioned error when I open the 2 projects in separate instances.

VS Code version: Code - Insiders 1.54.0-insider (9ecd3fc3022e8c154aff868f74bd5d77f7d4a2ea, 2021-02-23T10:46:22.816Z) OS version: Windows_NT x64 10.0.19042

System Info

Item	Value
CPUs	Intel® Core™ i5-8265U CPU @ 1.60GHz (8 x 1800)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: enabled rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.87GB (6.66GB free)
Process Argv	–crash-reporter-id 340e0eb9-5b34-4206-9e2e-bd86fc3b2cf3
Screen Reader	no
VM	0%

Extensions (24)

Extension	Author (truncated)	Version
ng-template	Ang	11.2.3
vscode-eslint	dba	2.1.14
gitlens	eam	11.2.1
EditorConfig	Edi	0.16.4
vscode-npm-script	eg2	0.3.16
prettier-vscode	esb	5.9.2
vscode-pull-request-github	Git	0.23.1
output-colorizer	IBM	0.1.2
typescript-javascript-grammar	ms-	0.0.55
vscode-js-profile-flame	ms-	0.0.14
vscode-typescript-next	ms-	4.3.20210223
vscode-typescript-tslint-plugin	ms-	1.3.3
cordova-tools	msj	2.2.0
debugger-for-chrome	msj	4.12.12
vscode-react-native	msj	1.4.0
vscode-commons	red	0.0.4
vscode-xml	red	0.15.0
vscode-yaml	red	0.15.0
sonarlint-vscode	Son	1.20.1
code-spell-checker	str	1.10.2
vscode-stylelint	sty	0.86.0
vscodeintellicode	Vis	1.2.11
glean	wix	5.1.1
vscode-import-cost	wix	2.15.0

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30260314
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
core-portspanel:30257802
pythontb:30258533
wslfolderdoccf:30257852
vscoresta800cf:30263255

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 31 (8 by maintainers)

Most upvoted comments

Totally broken I’m afraid - frozen terminal with no way of creating new ones. Let me do some more testing and I’ll update https://github.com/microsoft/vscode/issues/119090 with my findings.

zinderic on Mar 16, 2021

I get this error several times an hour at which point I have to open a new terminal to get anything done. Truly broken.

Version: 1.54.1 Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8 Date: 2021-03-04T22:42:18.719Z (1 wk ago) Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Darwin x64 20.3.0

pvogel1967 on Mar 12, 2021

~~I would suggest to update to latest version:~~

Version: 1.54.2
Commit: fd6f3bce6709b121a895d042d343d71f317d74e7
Date: 2021-03-11T00:56:09.783Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0

~~At least on a Mac I’ve been running it for more than 24 hours without having any issues with my terminals or seeing the error message. It’s working great.~~

Update: actually no, as soon as I started using it more actively I started seeing the message and the terminals started hanging again. The problem is not resolved in this version.

zinderic on Mar 13, 2021

Version: 1.54.0 Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8 Date: 2021-03-04T22:42:18.719Z (6 days ago) Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Darwin x64 20.3.0

Same issue when having 2 VS Code windows open

richardsimko on Mar 11, 2021

It seems fixed in latest insider version:

Version: 1.55.0-insider (Universal)
Commit: 5d80c30e5b6ce8b2f5336ed55ad043490b0b818f
Date: 2021-03-08T05:24:34.127Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0

I was able to reproduce it with the version before that one. Now after the update it’s running for few hours without seeing the error and the terminal is responsive.

zinderic on Mar 8, 2021

I have encountered the same “disconnection” problem soon after Visual Studio finished to update today.

Version: 1.54.1 (user setup) Commit: f30a9b73e8ffc278e71575118b6bf568f04587c8 Date: 2021-03-04T22:38:31.419Z Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Windows_NT x64 10.0.19042

violacambie on Mar 5, 2021

@Tyriar , after the latest install i am not able to replicate the issue. i would like to observe this at least today and tomorrow if its okay with you.

sanket-bhalerao on Feb 26, 2021