starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Experenced visual lag when upgrade to Win 10 v2004 #6885

New Issue
Closed
opened 2026-01-31 00:49:43 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 00:49:43 +00:00
Owner
Copy Link

Originally created by @jasl on GitHub (Mar 15, 2020).

Environment

Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal (Preview) installed from Microsoft Store, version: 0.9.433.0

Intel Core i9 9900K and Nvidia Geforce 2080 Ti (with latest driver), hardwares are powerful enough and well maintained.

Steps to reproduce

  • Upgrade to Win10 v2004 from v1909
  • Open Windows Terminal

Expected behavior

Windows Terminal should smoothy all the time

Actual behavior

When the terminal window is the active window, I experienced a visual lag, especially when mouse moving and draging the terminal window, not smoothy clearly.

When draging the Terminal window, in TaskMgr I can see the power consumption status of Windows Terminal process from very low changing to very high quickly.

When the Terminal not the active window (e.g switch to other window or open Start menu), the lag disappeared.

This problem ONLY occured on Window Terminal, I don't see other application or Windows bundled have this problem.

Originally created by @jasl on GitHub (Mar 15, 2020). # Environment Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal (Preview) installed from Microsoft Store, version: 0.9.433.0 Intel Core i9 9900K and Nvidia Geforce 2080 Ti (with latest driver), hardwares are powerful enough and well maintained. # Steps to reproduce - Upgrade to Win10 v2004 from v1909 - Open Windows Terminal # Expected behavior Windows Terminal should smoothy all the time # Actual behavior When the terminal window is the active window, I experienced a visual lag, especially when mouse moving and draging the terminal window, not smoothy clearly. When draging the Terminal window, in TaskMgr I can see the power consumption status of Windows Terminal process from very low changing to very high quickly. When the Terminal not the active window (e.g switch to other window or open Start menu), the lag disappeared. This problem ONLY occured on Window Terminal, I don't see other application or Windows bundled have this problem.
claunia added the Resolution-Duplicate label 2026-01-31 00:49:43 +00:00
claunia commented 2026-01-31 00:49:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

Are you using acrylic transparency?

@DHowett-MSFT commented on GitHub (Mar 16, 2020): Are you using acrylic transparency?
claunia commented 2026-01-31 00:49:44 +00:00
Author
Owner
Copy Link

@jasl commented on GitHub (Mar 16, 2020):

Are you using acrylic transparency?

I guess this originally, then I tried to set transparency to 1.0 (I think this should disable acrylic effect), but lag still

@jasl commented on GitHub (Mar 16, 2020): > Are you using acrylic transparency? I guess this originally, then I tried to set transparency to 1.0 (I think this should disable acrylic effect), but lag still
claunia commented 2026-01-31 00:49:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

Unfortunately, useAcrylic still applies even if the opacity is 1.0; can you try setting useAcrylic to false?

@DHowett-MSFT commented on GitHub (Mar 16, 2020): Unfortunately, `useAcrylic` still applies even if the opacity is `1.0`; can you try setting useAcrylic to false?
claunia commented 2026-01-31 00:49:45 +00:00
Author
Owner
Copy Link

@jasl commented on GitHub (Mar 16, 2020):

Unfortunately, useAcrylic still applies even if the opacity is 1.0; can you try setting useAcrylic to false?

just confirmed I already set useAcrylic to false

@jasl commented on GitHub (Mar 16, 2020): > Unfortunately, `useAcrylic` still applies even if the opacity is `1.0`; can you try setting useAcrylic to false? just confirmed I already set `useAcrylic` to `false`
claunia commented 2026-01-31 00:49:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 17, 2020):

Thanks for confirming. Until proven otherwise, I'm going to call this one a /dupe of #778. Once we've optimized how many pixels we push through the GPU (which right now is "the whole screen, every single time even one of them changes"), we can talk about individual performance issues.

Thanks!

@DHowett-MSFT commented on GitHub (Mar 17, 2020): Thanks for confirming. Until proven otherwise, I'm going to call this one a /dupe of #778. Once we've optimized how many pixels we push through the GPU (which right now is "the whole screen, every single time even one of them changes"), we can talk about individual performance issues. Thanks!
claunia commented 2026-01-31 00:49:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 17, 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 (Mar 17, 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!
claunia commented 2026-01-31 00:49:45 +00:00
Author
Owner
Copy Link

@nikita240 commented on GitHub (Apr 9, 2020):

+1

Just upgraded Windows to 2004 insiders preview. Terminal is completely unusable now. Awful stutter and lag.

i7-8750H and RTX 2080 Max-Q

@nikita240 commented on GitHub (Apr 9, 2020): +1 Just upgraded Windows to 2004 insiders preview. Terminal is completely unusable now. Awful stutter and lag. i7-8750H and RTX 2080 Max-Q
claunia commented 2026-01-31 00:49:45 +00:00
Author
Owner
Copy Link

@brian316 commented on GitHub (Mar 31, 2021):

Lags with or without acrylic mode. Using dev version of windows insider

@brian316 commented on GitHub (Mar 31, 2021): Lags with or without acrylic mode. Using dev version of windows insider
claunia commented 2026-01-31 00:49:46 +00:00
Author
Owner
Copy Link

@alexcochran commented on GitHub (Jun 29, 2021):

+1

Windows Terminal stutters and lags pretty badly for me (Ryzen 9 3900X, NVIDIA 2060S, Windows 10.0.19041). GPU usage notification from NVIDIA always shows up when I start the program. I tried altering the 3D settings for the Terminal application in the NVIDIA Control Panel to only use "Fixed Refresh" (this has worked for other applications) but to no avail.

@alexcochran commented on GitHub (Jun 29, 2021): +1 Windows Terminal stutters and lags pretty badly for me (Ryzen 9 3900X, NVIDIA 2060S, Windows 10.0.19041). GPU usage notification from NVIDIA always shows up when I start the program. I tried altering the 3D settings for the Terminal application in the NVIDIA Control Panel to only use "Fixed Refresh" (this has worked for other applications) but to no avail.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6885
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?