Connection to terminal's pty host process is becoming unresponsive
See original GitHub issueIssue Type: Bug
After updating to latest VSCode stable (1.59) I started encountering an error when running tasks (The connection to the terminal’s pty host process is unresponsive, the terminals may stop working.). This used to work fine on 1.58.2 and I confirmed that it is broken on latest insider build too (1.60.0)
I have a bunch of VSCode tasks for ‘orchestrating’ local docker setup, so I can run some commands to run builds and generate TypeScript clients directly from the UI. When I run tasks without any “dependsOn” tasks they run fine. If one task depends on single other task, it also runs fine. I have problems when single task have multiple entries in “dependsOn” section - it usually works fine for the first time after I open VSCode but then the issue happens and I have to fully restart VSCode to make it work again.
VS Code version: Code - Insiders 1.60.0-insider (49af1cbe00271ac2ea36cfc5f7352fe31a7b0094, 2021-08-06T06:41:50.275Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No
System Info
Item | Value |
---|---|
CPUs | AMD Ryzen 9 3900X 12-Core Processor (24 x 3800) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 31.93GB (18.13GB free) |
Process Argv | –crash-reporter-id 99c6e3ee-c17a-4f3a-a118-c9cbac23e0db |
Screen Reader | no |
VM | 0% |
Extensions (1)
Extension | Author (truncated) | Version |
---|---|---|
csharp | ms- | 1.23.14 |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
pythonvspyt551:30291412
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
pythonvsuse255:30319630
vscod805:30301674
pythonvspyt200:30323110
vsccppwt:30312692
pythonvssor306:30340298
bridge0708:30335490
pygetstartedt2:30348854
dockerwalkthru:30348713
Tasks hierarchy
{
"label": "[Debug] Create base image for Api container",
"command": "powershell",
"args": [
"docker",
"build",
"--rm",
"-f",
"${workspaceFolder}/BaseImage.Debug.Dockerfile",
"-t",
"baseimage-api-debug:latest",
"."
]
},
{
"label": "[Debug] Create image for Api.Dockerfile",
"command": "powershell",
"args": [
"docker",
"build",
"--rm",
"-f",
"${workspaceFolder}/Api.Dockerfile",
"-t",
"backend-core-debug:latest",
"."
],
"problemMatcher": {
"base": "$msCompile",
"fileLocation": [
"relative",
"${workspaceRoot}"
]
},
"dependsOn": [
"[Debug] Create base image for Api container"
]
},
{
"label": "[Debug] Create image for Hangfire.Server.Dockerfile",
"command": "powershell",
"args": [
"docker",
"build",
"--rm",
"-f",
"${workspaceFolder}/Hangfire.Server.Dockerfile",
"-t",
"hangfire-server-debug:latest",
"."
],
"problemMatcher": {
"base": "$msCompile",
"fileLocation": [
"relative",
"${workspaceRoot}"
]
},
"dependsOn": [
"[Debug] Create base image for Api container"
]
},
{
"label": "[Debug] Create service for docker-compose.dev.yml",
"command": "powershell",
"args": [
"docker-compose",
"-f",
"${workspaceFolder}/docker-compose.dev.yml",
"up",
"-d",
"--build",
"--force-recreate",
"--renew-anon-volumes"
],
"problemMatcher": "$msCompile",
"dependsOn": [
"[Debug] Create image for Api.Dockerfile",
"[Debug] Create image for Hangfire.Server.Dockerfile"
]
},
{
"label": "[TS] generate libraries",
"type": "shell",
"command": "\"${workspaceRoot}/../_scripts/wait-for-it-http.ps1\" && nswag.cmd run || docker logs backend-core_api_1",
"problemMatcher": "$msCompile",
"options": {
"cwd": "${workspaceRoot}/../tt-ts-core"
},
"dependsOn": [
"[Debug] Create service for docker-compose.dev.yml"
]
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:39 (6 by maintainers)
Top GitHub Comments
restart vs code …
This is unbelievably frustrating… After a clean install of latest Insiders the warning pops up without even starting the terminal in the first place! I have no extensions installed, nothing. It’s clean as possible. What is going on? Anyone else struggling with this?