Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.119.1
- Commit: 974500e64f0d1cfdf7c9821a2a51c2cb3bf0e561
- Date: 2026-05-12T01:20:22+09:00
- Electron: 39.8.8
- ElectronBuildId: 13870025
- Chromium: 142.0.7444.265
- Node.js: 22.22.1
- V8: 14.2.231.22-electron.0
- OS Version: macOS 15.7, Darwin arm64 24.6.0
Steps to Reproduce:
- Open a project in VS Code.
- Start the project from the integrated terminal using a Node.js process.
- Leave the project running for some time.
- Observe that the integrated terminal starts showing stale colored rendering artifacts.
Expected:
The integrated terminal should only display the current terminal buffer and should not leave stale colored blocks or floating characters in the viewport.
Actual:
The integrated terminal intermittently shows stale red blocks/lines and a floating yellow character after the project has been running for a while. In the screenshot, two node terminals are open and the terminal panel shows red rectangular artifacts on the left and near the terminal split area, plus a small yellow 5 near the top center of the terminal viewport.
Additional context:
This does not appear to be caused by extensions. I do not yet have a minimal deterministic reproduction case because the issue appears after the project has been running for a while.

Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Expected:
The integrated terminal should only display the current terminal buffer and should not leave stale colored blocks or floating characters in the viewport.
Actual:
The integrated terminal intermittently shows stale red blocks/lines and a floating yellow character after the project has been running for a while. In the screenshot, two
nodeterminals are open and the terminal panel shows red rectangular artifacts on the left and near the terminal split area, plus a small yellow5near the top center of the terminal viewport.Additional context:
This does not appear to be caused by extensions. I do not yet have a minimal deterministic reproduction case because the issue appears after the project has been running for a while.