The connection to the terminal's pty host process is unresponsive, the terminals may stop working.

[ZedRover]

• VSCode Version: 1.78.2 Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
• Local OS Version: Apple M1 Pro, 13.4 (22F66)
• Remote OS Version: Ubuntu 18.04
• Remote Extension/Connection Type: Containers

• Logs:

Steps to Reproduce:
After connecting to the docker container with ssh for python development, I only need to execute python scripts like "python train.py" on the command line. I often encounter problems with the pty host disconnecting, or the built-in command line is very laggy, I am now used to local I'm now used to running python scripts in the local terminal, but I hope the vscode team will fix this bug.
I run into this problem both in my corporate intranet environment and at home when developing remotely via tailscale intranet penetration, and I'm sure it's not due to network issues. Also, my remote server has 4Tb RAM, which I don't normally think is related to the remote server configuration.

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

[ZedRover]

https://github.com/microsoft/vscode/issues/150058
https://github.com/microsoft/vscode-remote-release/issues/8050
According to the developer this issue has been fixed, but I'm still experiencing this problem a lot lately. I'm looking forward for your help.

[topmask]

I have also encountered this problem and cannot solve it.

[s3bc40]

Same here for VS Code 1.79

[toasteur]

same problem here on windows 10 as soon as i updated to 1.79

P.S: reverted to 1.78.2, works again.

[draganpetkov]

I have the same problem on the new update.

Version: 1.79.0
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows 11

[lucasgustavodiaz]

Same problem here, clean install

Versión: 1.79.1 (user setup)
Electrón: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621

PD: The only way to avoid the message is by killing the vscode terminal before exiting, at the next start the message does not appear. As long as we close the terminal before leaving, otherwise the problem persists

[draganpetkov]

I reverted to an older version until the bug is fixed

[Tyriar]

/duplicate microsoft/vscode#130320