vscode: Terminal in Editor rendering errors and disposed errors

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.63.0 (user setup)
OS Version: Windows 10

Steps to Reproduce:

Set the setting: "terminal.integrated.defaultLocation": "editor",
Open a new terminal (should open in editor).
- Error Notification: Terminal with ID 4 does not exist (has it already been disposed?)
Open another new terminal in the editor.
- Same message shows up
Drag split the terminal window to below.
- content disappears from the bottom terminal, and is non interactive

I’m mostly repro-ing this with the WSL2 extension, but also happens with the standard windows powershell.

I also separately have VSCode Insiders installed, and have been seeing this since last month on the Insiders release. This issue has started happening in the standard release channel for me starting from yesterday’s update.

This also happens on a fresh insiders install, and def with the wsl extension.

VS Code version: Code 1.63.0 (7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e, 2021-12-07T06:26:56.179Z) OS version: Windows_NT x64 10.0.19043 Restricted Mode: No

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 2
Comments: 15 (10 by maintainers)

Commits related to this issue

fix #138601 fix #138770 — committed to microsoft/vscode by meganrogge 3 years ago

Most upvoted comments

merged into the release branch

meganrogge on Dec 14, 2021

I am also experiencing this error on Mac after installing the latest update.

I get this error whenever opening a new terminal in the editor, even immediately after a relaunch. Terminals in the panel do not appear to be affected.

Version: 1.63.0
Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
Date: 2021-12-07T05:15:48.091Z (2 days ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 18.7.0

atg on Dec 9, 2021