Poor graphics rendering performance in Windows when Terminal is the foreground/active app #9903

Closed
opened 2026-01-31 02:07:01 +00:00 by claunia · 5 comments
Owner

Originally created by @afefer on GitHub (Jul 28, 2020).

Environment

Windows build number: 10.0.19041.388
Windows Terminal version (if applicable): 1.1.2021.0
CPU: Ryzen 9 9300X
GPU: GeForce 2080 Ti
Monitor settings: 3840x1600 @ 144 Hz w/ Nvidia G-Sync enabled

Steps to reproduce

  1. Open Windows Terminal and ensure Terminal is the foreground (active selected) app.
  2. Move mouse cursor OR shake Terminal to minimize all other apps on screen.

Expected behavior

General rendering performance in Windows should not be affected by Terminal.

Actual behavior

The mouse cursor appears slow/choppy when Terminal is in the foreground, and the problem immediately goes away when you click on another window to make Terminal no longer the foreground app. This problem not only affects the rendering of the mouse cursor, but other graphics as well (e.g. if you shake the Terminal window to auto-minimize all other open apps, the visual effects for the minimize action also appears sluggish).

Note this can also be repro'd when Terminal is minimized and the taskbar icon is clicked to restore the app - the visual effects for the restore action is sluggish.

Originally created by @afefer on GitHub (Jul 28, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.388 Windows Terminal version (if applicable): 1.1.2021.0 CPU: Ryzen 9 9300X GPU: GeForce 2080 Ti Monitor settings: 3840x1600 @ 144 Hz w/ Nvidia G-Sync enabled ``` # Steps to reproduce 1. Open Windows Terminal and ensure Terminal is the foreground (active selected) app. 2. Move mouse cursor OR shake Terminal to minimize all other apps on screen. # Expected behavior General rendering performance in Windows should not be affected by Terminal. # Actual behavior The mouse cursor appears slow/choppy when Terminal is in the foreground, and the problem immediately goes away when you click on another window to make Terminal no longer the foreground app. This problem not only affects the rendering of the mouse cursor, but other graphics as well (e.g. if you shake the Terminal window to auto-minimize all other open apps, the visual effects for the minimize action also appears sluggish). Note this can also be repro'd when Terminal is minimized and the taskbar icon is clicked to restore the app - the visual effects for the restore action is sluggish.
claunia added the Resolution-Duplicate label 2026-01-31 02:07:01 +00:00
Author
Owner

@jack775544 commented on GitHub (Jul 28, 2020):

Almost certainly this issue https://github.com/microsoft/terminal/issues/649

Adding the setting "experimental.rendering.software": true is the recommended temporary workaround right now.

@jack775544 commented on GitHub (Jul 28, 2020): Almost certainly this issue https://github.com/microsoft/terminal/issues/649 Adding the setting `"experimental.rendering.software": true` is the recommended temporary workaround right now.
Author
Owner

@afefer commented on GitHub (Jul 28, 2020):

Yup, that looks like it. Thanks @jack775544 for the quick pointer to that bug. This can be closed as duplicate.

@afefer commented on GitHub (Jul 28, 2020): Yup, that looks like it. Thanks @jack775544 for the quick pointer to that bug. This can be closed as duplicate.
Author
Owner

@DHowett commented on GitHub (Jul 28, 2020):

/dup #649

@DHowett commented on GitHub (Jul 28, 2020): /dup #649
Author
Owner

@ghost commented on GitHub (Jul 28, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 28, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@DHowett commented on GitHub (Jul 28, 2020):

Thanks everyone!

@DHowett commented on GitHub (Jul 28, 2020): Thanks everyone!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9903