Change:
resolved "https://registry.yarnpkg.com/xterm-addon-unicode11/-/xterm-addon-unicode11-0.4.0-beta.5.tgz#3900e66f10d2e506133b61d7421aab6878d32665" integrity sha512-+g+fuxAd/tkCEJ/jhdnebXKtdPrhsu4VKWNnB/3qM35GbuGQOasmYFYnKL+HYZMpbQ6YqeZcXTVg/wnCTttz0g== <del> xterm-addon-webgl@0.13.0-beta.37: version "0.13.0-beta.37" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.13.0-beta.37.tgz#46819028abbe66cfabc60a615c4cc7bcd9156305" integrity sha512-XoJdN8CELScYLPnEJKo9s0r3tC9/szGnmBEymV1+oLbMrQNeaV5VQqbiYzgKTyDHc12Gc5lPvih3/r6eL/9gig== </del> <ins> xterm-addon-webgl@0.13.0-beta.45: version "0.13.0-beta.45" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.13.0-beta.45.tgz#f1f3c08e2a819970c1af0362eeb61185babcb6fc" integrity sha512-TXq5mxvG2alo5hSj/aFqHDzR2RSV2HH4is7R7kVmSCVPnl2RgDfAPilXOEJyYFLF09EgiGiG5UZASYJjvJfMRg== </ins> <del> xterm@5.0.0-beta.36: version "5.0.0-beta.36" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.0.0-beta.36.tgz#c07721d04fddc0f86417bc95a2f0824040c0eca9" integrity sha512-6aND1UOAcCn42WlVrQbIU7a+ZFD4o3Gy2yE1BeDLTCFfK6oqc1QpRrH1plGOUypeabxCTADrw5vhl5W/45kutg== </del> <ins> xterm@5.0.0-beta.44: version "5.0.0-beta.44" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.0.0-beta.44.tgz#854ed16c06808295777afc4ef7b78ccd55e59d4a" integrity sha512-raKvoikUjKZTO9duYliDp5hSKAwYia9P51QCumHY30V/bRZ2fq9ryyKQ65PxW8LzGYK8o7x7vNRUHVWbS073Tw== </ins>

Discussion:
Testing Version: 1.71.0-insider Commit: Date: 2022-08-23T05:19:02.563Z Electron: 19.0.12 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 21.6.0 Sandboxed: Yes set setting terminal.integrated.gpuAcceleration: on in a terminal type: followed by and a new line ! Especially under the there's a lot of space so I would say it can't be antialiasing that interferes
Good find, the stroke seems oddly large on the here.
Upstream:
Looks better on the Mac now. !

Does this issue occur when all extensions are disabled?: Yes VS Code Version:1.70 OS Version: windows 10 Steps to Reproduce: I upgrade the vscode to 1.70 version it's terminal is seems performing slowly
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Please see for creating actionable performance problem issues. /label info-needed terminal
My team has been seeing a large slow down with the terminal when in a devcontainer's main project directory. It's fast once you leave it.
I just tried disabling newly enabled shellIntegration setting and it sped back up. Operating System: macOS 12.5 Hardware: MacBook Pro 13-inch, M1, 2020) 16 GB Memory Visual Studio Code: Version 1.70.0 Universal
what shell are you using?
zsh. My team is all on M1 MacBook Pro's. One person has oh-my-zsh installed. I have rocketship. The rest are stock. This is in a decent sized monorepo in a Node+TypeScript devcontainer. The same behavior does not appear in the stock/empty Node+TypScript devcontainer. I have not tried it locally (outside the container) as we don't work that way.
adding your comment from for more context:
I get the similar performance issue, using nushell, with MacBook Pro (not M1)
I'm also having bad performance with the new enabled with powershell on Windows 11; it manifests as a huge delay to focus the terminal, or the whole editor freezing and asking if I want to restart it, or, not even being able to launch a new terminal (the pane is blank). Sometimes when it happens, is using a large amount of CPU. The main problem is that it's intermittent and I can't seem go get a profile of it... but I'm trying.
I fixed several performance regressions in the last few days: , , I expect this to be fixed in v1.72 (September)
Can you please provides steps to verify this?
This is a bit hard to verify, but myself and have already tested it fairly thoroughly
Just commenting to give anecdotal data.

In 1.72.0 the example I gave in the duplicate issue now renders in 12-15 seconds depending on the run for an 11.8 second run with lots of text. Previously it was rendering in 39.7 seconds. The integrated terminal is definitely usable again, thanks! (at least on my box )