-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WT causes the whole Windows animation to be super laggy (after RDP?), until all the WT processes are terminated #18422
Comments
Thanks for filing! What hardware (specifically GPU(s)) are you using /? Can you also update your drivers (if you haven't already) and share what versions are installed? |
Sure, I will try if they help |
Unfortunately, changing graphics API to direct2D doesn't help. I will try the opacity trick next. |
Guys, I need some time to test and provide results. Not sure why a week is considered enough time to label an ongoing issue as "no activity" and be closed. |
Setting opacity to 99% does not help, either. |
Windows Terminal version
1.21.3231.0
Windows build number
10.0.19045.5247
Other Software
Command line
Steps to reproduce
There are no concrete steps to reproduce, as the issue occurs randomly. However, I’ve noticed two recurring patterns:
Expected Behavior
It shouldn't cause Windows animation lagging issue.
Actual Behavior
I briefly mentioned this performance issue [in another ticket](#17414 (comment)), but I believe it deserves its own standalone discussion.
When the bug occurs, the entire Windows desktop UI becomes extremely laggy (e.g., dragging and switching windows), with performance dropping to what feels like less than 20 FPS. 3D applications like full-screen games are not affected; only the desktop UI.
To resolve the issue, I must close all open Windows Terminal windows (I typically keep 2–3 open at any given time). Doing so immediately restores normal performance.
The issue is not tied to any specific tab—I’ve tested this by opening a new window and then closing all existing windows, but the problem persists.
Here’s what the processes related to WT look like before I terminate them (and fix the issue):
The text was updated successfully, but these errors were encountered: