Incorrect font characters rendered after running simple terminal stress program for a long time #21073

Closed
opened 2026-01-31 07:32:22 +00:00 by claunia · 3 comments
Owner

Originally created by @Treit on GitHub (Jan 8, 2024).

Windows Terminal version

1.19.3172.0

Windows build number

10.0.26020.0

Other Software

No response

Steps to reproduce

Run the TerminalStress program in a pane and let it run for a long time (for instance, overnight.)

The next morning, press ctrl+C.

Type something like "cd c:"

Notice that it is actually rendered in the terminal as:

cd c:Ö

Expected Behavior

Running a program that prints lots of random stuff to the terminal should not affect how characters are rendered after the program quits.

Actual Behavior

Certain characters are now rendered incorrectly. For instance, typing the following sequence:

~@|\[]{}

is now displayed as:

ß§ÄÜäüöÖ
Originally created by @Treit on GitHub (Jan 8, 2024). ### Windows Terminal version 1.19.3172.0 ### Windows build number 10.0.26020.0 ### Other Software _No response_ ### Steps to reproduce Run the [TerminalStress](https://github.com/microsoft/terminal/blob/main/src/tools/TerminalStress/Program.cs) program in a pane and let it run for a long time (for instance, overnight.) The next morning, press ctrl+C. Type something like "cd c:\" Notice that it is actually rendered in the terminal as: ``` cd c:Ö ``` ### Expected Behavior Running a program that prints lots of random stuff to the terminal should not affect how characters are rendered after the program quits. ### Actual Behavior Certain characters are now rendered incorrectly. For instance, typing the following sequence: ``` ~@|\[]{} ``` is now displayed as: ``` ß§ÄÜäüöÖ ```
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:32:22 +00:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 8, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Jan 8, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Font rendering issues in Terminal (#610)](https://github.com/microsoft/terminal/issues/610), similarity score: 0.76 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Author
Owner

@DHowett commented on GitHub (Jan 8, 2024):

Honestly, this is probably VT character sets getting activated!

image

@DHowett commented on GitHub (Jan 8, 2024): Honestly, this is probably VT character sets getting activated! ![image](https://github.com/microsoft/terminal/assets/189190/e3b316aa-b281-4e52-a408-8eabb05aefaf)
Author
Owner

@DHowett commented on GitHub (Jan 8, 2024):

There's a whole bunch of them supported by SCS, FWIW, in case those glyphs don't look like the ones you're seeing.

Printing out unguarded escape sequences can always leave your terminal in a weird state!

@DHowett commented on GitHub (Jan 8, 2024): There's a [whole bunch of them supported by `SCS`](https://vt100.net/docs/vt510-rm/SCS.html), FWIW, in case those glyphs don't look like the ones you're seeing. Printing out unguarded escape sequences can always leave your terminal in a weird state!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21073