Change:
"@vscode/windows-mutex": "^0.5.0", "@vscode/windows-process-tree": "^0.6.0", "@vscode/windows-registry": "^1.1.0", <del> "@xterm/addon-canvas": "0.6.0-beta.31", "@xterm/addon-image": "0.7.0-beta.29", "@xterm/addon-search": "0.14.0-beta.31", "@xterm/addon-serialize": "0.12.0-beta.31", "@xterm/addon-unicode11": "0.7.0-beta.31", "@xterm/addon-webgl": "0.17.0-beta.31", "@xterm/headless": "5.4.0-beta.31", "@xterm/xterm": "5.4.0-beta.31", </del> <ins> "@xterm/addon-canvas": "0.6.0-beta.33", "@xterm/addon-image": "0.7.0-beta.31", "@xterm/addon-search": "0.14.0-beta.33", "@xterm/addon-serialize": "0.12.0-beta.33", "@xterm/addon-unicode11": "0.7.0-beta.33", "@xterm/addon-webgl": "0.17.0-beta.33", "@xterm/headless": "5.4.0-beta.33", "@xterm/xterm": "5.4.0-beta.33", </ins> "graceful-fs": "4.2.11", "http-proxy-agent": "^7.0.0", "https-proxy-agent": "^7.0.2",

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.85.2 OS Version: windows 10 Steps to Reproduce: focus to a running terminal tab : anti aliasing looks activated there are spaces between the characters 2 The terminal is running correctly 3 to fix it, I can close and reopen the terminal change some settings of the terminal (curson blink on/off for example) ! Now that i'm thinking about, maybe it's because I previously connect to my PC from remote RDP ? Version: 1.85.2 Commit: Date: 2024-01-18T06:40:10.514Z Electron: 25.9.7 ElectronBuildId: Chromium: 114.0.5735.289 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
I cannot reproduce. Can you in insiders?
I see the same thing on Mac. It happens after VSCode has been running for a while. The only real setting I've tweaked is that I've set my scrollback to . Below is a screenshot of a newly opened terminal next to the old one, which will work fine for some time. Eventually they all become like this and I need to restart them.

Confirmed that toggling the cursor blink setting resets these terminals to a working state. <img width="905" alt="image" src=""
Here's some debugging info, hopefully it helps. I dumped the styles from the div that holds the terminal window: And from the div, styles
The problem appears to be this style. If I toggle the style rule, the terminal appears to be fixed: <img width="239" alt="image" src=""I'm not sure why, but only the terminals that are in an accessible mode (why are some of them switching to be accessible?) seem to be broken.
Can it be connected to a previous remote desktop connection to the PC running vscode ? When connecting and disconnecting, the resolution change and, maybe, the terminal is not refresh correctly ? Are you using such a remote desktop connection on your mac when it happend ?
I'm not using any sort of remote desktop. It just appears that a terminal "rots" after being in the background long enough (maybe the laptop going to sleep?).
Have had same issue for weeks
What do you mean by terminals in accessible mode?
Hi So it happend to me often without RDP before or switching reslution - what can I save or check to help here ?
It appears the affected terminal is switching from a canvas/GPU renderer to an HTML renderer. There are a few accessibility messages scattered around the terminals that switch when browsing the DOM. I am not sure how any of the terminal rendering code works, so that's just a guess that it's accessibility.
I've been seeing this issue randomly for the better part of a year: ! Not sure what causes it. It seems to occur with long-running terminal sessions, after some time has passed. In my case, they are training runs for machine learning. I'm using Code-OSS on Arch Linux with x11. This seems to happen more frequently when my system "freezes", for whatever reason. While doing ML, my system will often hang, as weights are written to disk, or big pages are swapped between memory/disk. During this time, my entire system becomes unresponsive, as those tasks take priority. It is EXTREMELY COMMON for this issue to occur just after that happens. Though it will only affect 1 or 2 terminals, typically; not all of them.

There's also an uncommon version of this bug, where the extra spaces are not distributed uniformly, as you see here. Instead, there might be 1 or 2 extra "columns" of spaces splitting the terminal, in random positions. But otherwise, the rest of the text looks fine - except for a few columns of whitespace.
This is new info for me, I was not aware of letter-spacing to looks like this. Perhaps something is going wrong here:
Let me know if you'd like me to set a breakpoint somewhere and monitor a running instance. For now I'll try to set a breakpoint on that line and see if I can get you the cached W width.
Reproduced just now: 3 terminals showing from gpu accel on to off 2 terminals, the last one had the spaced wrong ! Selection is showing wrong: ! Width cache: ! High letter spacing: !
The letter spacing is determined by this line: The width cache gives 0: !
Width cache : !
should fix it
Thank you, Appreciate the investigation and fix.