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

Weird rendering issue where artifacts appear and slowly brighten over time #10057

New Issue
Open
opened 2026-01-31 02:11:27 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:11:27 +00:00
Owner
Copy Link

Originally created by @anomaly256 on GitHub (Aug 7, 2020).

Environment

Win32NT 10.0.20175.0 Microsoft Windows NT 10.0.20175.0

Windows Terminal version:
Version: 1.1.2021.0
Version: 1.1.2022.0

WSL2, Powershell, cmd

Steps to reproduce

Launch terminal with any available shell, wait a few seconds.

Expected behavior

The rendered text renders correctly

Actual behavior

The text slowly brightens, as if some shader is accumulating error? This is more noticable
in shells with coloured text, though it is still visible with the standard light gray on back
command promp colours. This rapidly begins appear as artifacts and 'spots' on the text.
I've tested with the Terminal release and Terminal previews, both exhibit this behaviour. I didn't notice a difference between 'Acrylic' enabled or not in settings.json.

terminal 1
terminal 2
terminal 3

The screengrabs above show first version 1.1.2021.0 with a fresh tab, then the same tab a few seconds later after the issue has manifested, then finally a screengrab of 1.1.2022.0 newly installed showing the same issue with a fresh, unmodified settings.json

Originally created by @anomaly256 on GitHub (Aug 7, 2020). # Environment Win32NT 10.0.20175.0 Microsoft Windows NT 10.0.20175.0 Windows Terminal version: Version: 1.1.2021.0 Version: 1.1.2022.0 WSL2, Powershell, cmd # Steps to reproduce Launch terminal with any available shell, wait a few seconds. # Expected behavior The rendered text renders correctly # Actual behavior The text slowly brightens, as if some shader is accumulating error? This is more noticable in shells with coloured text, though it is still visible with the standard light gray on back command promp colours. This rapidly begins appear as artifacts and 'spots' on the text. I've tested with the Terminal release and Terminal previews, both exhibit this behaviour. I didn't notice a difference between 'Acrylic' enabled or not in settings.json. ![terminal 1](https://user-images.githubusercontent.com/421854/89646788-c87b3800-d8ff-11ea-9ca9-cc95cc364b29.png) ![terminal 2](https://user-images.githubusercontent.com/421854/89646786-c7e2a180-d8ff-11ea-9cfd-deedff1a7cf2.png) ![terminal 3](https://user-images.githubusercontent.com/421854/89646784-c74a0b00-d8ff-11ea-956d-ecf710203199.png) The screengrabs above show first version 1.1.2021.0 with a fresh tab, then the same tab a few seconds later after the issue has manifested, then finally a screengrab of 1.1.2022.0 newly installed showing the same issue with a fresh, unmodified settings.json
claunia commented 2026-01-31 02:11:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 7, 2020):

Well that's super bizarre. It kinda reminds me of the "melting text" issues we had a few releases back.

Could you try enabling either of the following two settings, and see if that changes anything?

"experimental.rendering.forceFullRepaint": true
"experimental.rendering.software": true

(see: https://docs.microsoft.com/en-us/windows/terminal/customize-settings/global-settings#rendering-settings)

@zadjii-msft commented on GitHub (Aug 7, 2020): Well that's super bizarre. It kinda reminds me of the "melting text" issues we had a few releases back. Could you try enabling either of the following two settings, and see if that changes anything? ```json "experimental.rendering.forceFullRepaint": true "experimental.rendering.software": true ``` (see: https://docs.microsoft.com/en-us/windows/terminal/customize-settings/global-settings#rendering-settings)
claunia commented 2026-01-31 02:11:28 +00:00
Author
Owner
Copy Link

@anomaly256 commented on GitHub (Aug 7, 2020):

Hi, thanks for looking into this. Enabling either one of those does appear to prevent the issue for both versions

@anomaly256 commented on GitHub (Aug 7, 2020): Hi, thanks for looking into this. Enabling either one of those does appear to prevent the issue for both versions
claunia commented 2026-01-31 02:11:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 7, 2020):

Huh, that makes me think it might have something to do with your graphics card / driver. What GPU do you have?

@zadjii-msft commented on GitHub (Aug 7, 2020): Huh, that makes me think it might have something to do with your graphics card / driver. What GPU do you have?
claunia commented 2026-01-31 02:11:29 +00:00
Author
Owner
Copy Link

@anomaly256 commented on GitHub (Aug 7, 2020):

It’s a laptop with intel iGPU and an nvidia gtx1060m, using latest oem drivers for both (not the laptop vendor’s outdated drivers). To be honest I’m not sure which gpu it was rendering on at the time but I can test that tomorrow and report back if it’s device specific

@anomaly256 commented on GitHub (Aug 7, 2020): It’s a laptop with intel iGPU and an nvidia gtx1060m, using latest oem drivers for both (not the laptop vendor’s outdated drivers). To be honest I’m not sure which gpu it was rendering on at the time but I can test that tomorrow and report back if it’s device specific
claunia commented 2026-01-31 02:11:29 +00:00
Author
Owner
Copy Link

@anomaly256 commented on GitHub (Aug 10, 2020):

When Terminal is forced to use the Intel iGPU the problem does not occur at all. When forced to the Nvidia GTX1060 then the problem manifests.

Using Nvidia driver 451.67, current WHQL stable version

@anomaly256 commented on GitHub (Aug 10, 2020): When Terminal is forced to use the Intel iGPU the problem does not occur at all. When forced to the Nvidia GTX1060 then the problem manifests. Using Nvidia driver 451.67, current WHQL stable version
claunia commented 2026-01-31 02:11:29 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 14, 2020):

So, I'm going to put this on our issue backlog and take Triage off it, but add "Needs repro" -- I have no idea what we need to do to get this going, but wow, that's really unusual.

@DHowett commented on GitHub (Aug 14, 2020): So, I'm going to put this on our issue backlog and take Triage off it, but add "Needs repro" -- I have no idea what we need to do to get this going, but wow, that's really unusual.
claunia commented 2026-01-31 02:11:29 +00:00
Author
Owner
Copy Link

@anomaly256 commented on GitHub (Aug 14, 2020):

No worries. I've tried to repro on other hosts with nvidia graphics, on this build of windows with this driver version and it's not manifesting. It might be something specific to hybrid graphics, or this silicon or video card firmware. You've given me a workaround though with experimental.rendering.forceFullRepaint, thanks

@anomaly256 commented on GitHub (Aug 14, 2020): No worries. I've tried to repro on other hosts with nvidia graphics, on this build of windows with this driver version and it's not manifesting. It might be something specific to hybrid graphics, or this silicon or video card firmware. You've given me a workaround though with `experimental.rendering.forceFullRepaint`, thanks
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 Area-Rendering Help Wanted Issue-Bug Needs-Repro Priority-3 Product-Terminal
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#10057
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?