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

Bug Report - WSL based text rendering lag #2858

New Issue
Closed
opened 2026-01-30 23:07:15 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 23:07:15 +00:00
Owner
Copy Link

Originally created by @Sid911 on GitHub (Jul 20, 2019).

Environment

Windows build number: 18362.239
Windows Version: 1903
Windows Terminal version : 0.2.1831.0

Any other software?

Using WSL 1 with Ubuntu Distribution (just for info)

Steps to reproduce

This is the way I found it was most noticeable and also how I found it initially

  • Open Terminal
  • Open WSL Ubuntu using the options tab or type wsl.exe -d Ubuntu in CMD or Powershell
  • Install cmatrix using sudo apt install cmatrix
  • Type cmatrix to run.
  • See the laging behavior of the terminal.

Optional Reproducible Behavior

  • Now try to close the tab or application after running the cmatrix for a little while in full screen
  • The application Crashes or becomes unresponsive

This can also be seen a little bit when installing small files where ### lagS out significantly in WSL although I haven't noticed a crash just while installing things which is already rare compared to running cmatrix

Expected behavior

There shouldn't be any kind of this behavior where text lags out very well compared to other terminals. And it should defenitly not become unresponsive if we try to close the tab while doing so.

Actual behavior

Right now in its current State the Terminal uses very high resources while doing cmatrix, which is about 30% CPU usage OR more (depending on the size of the terminal). Which is higher than the number I saw with older versions of Terminal about 20-ish

It visibly lags while doing normal tasks like installing a package or any task where lots of lines update quickly, which kind of frustrating. A little bit but still.
In the case of crashing ** THE ENTIRE TERMINAL ** after trying to close the tab, I never did any serious task while executing "cmatrix" 😂😛 but that could end up very bad as the entire terminal crashes.

Here is one of multiple times it crashed.
image

Verifications

I have verified that its not my computer specific issue because cmatrix works like charm in other terminals like CMD, Powershell, Ubuntu Base Terminal, Hyper.

Correlating to that its not WSL issue because it works just fine on other terminals.
This is also a fresh install of windows, so I don't expect there are any issues here, not that it should matter.

Originally created by @Sid911 on GitHub (Jul 20, 2019). # Environment ```none Windows build number: 18362.239 Windows Version: 1903 Windows Terminal version : 0.2.1831.0 Any other software? Using WSL 1 with Ubuntu Distribution (just for info) ``` # Steps to reproduce _This is the way I found it was most noticeable and also how I found it initially_ - Open Terminal - Open WSL Ubuntu using the options tab or type ```wsl.exe -d Ubuntu``` in CMD or Powershell - Install cmatrix using ```sudo apt install cmatrix``` - Type ```cmatrix``` to run. - See the laging behavior of the terminal. ### Optional Reproducible Behavior - Now try to close the tab or application after running the cmatrix for a little while in full screen - The application Crashes or becomes unresponsive **This can also be seen a little bit when installing small files where** ```###``` **lagS out significantly in WSL although I haven't noticed a crash just while installing things which is already rare compared to running cmatrix** # Expected behavior There shouldn't be any kind of this behavior where text lags out very well compared to other terminals. And it should defenitly not become unresponsive if we try to close the tab while doing so. # Actual behavior Right now in its current State the Terminal uses very high resources while doing cmatrix, which is about 30% CPU usage OR more _(depending on the size of the terminal)_. Which is higher than the number I saw with older versions of Terminal _about 20-ish_ It visibly lags while doing normal tasks like installing a package or any task where lots of lines update quickly, which kind of frustrating. A little bit but still. In the case of crashing ** THE ENTIRE TERMINAL ** after trying to close the tab, I never did any serious task while executing "cmatrix" 😂😛 but that could end up very bad as the entire terminal crashes. Here is one of multiple times it crashed. ![image](https://user-images.githubusercontent.com/27860105/61579965-ce05b480-ab29-11e9-908d-07c8e4c149a4.png) # Verifications I have verified that its not my computer specific issue because cmatrix works like charm in other terminals like CMD, Powershell, Ubuntu Base Terminal, Hyper. Correlating to that its not WSL issue because it works just fine on other terminals. This is also a fresh install of windows, so I don't expect there are any issues here, not that it should matter.
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 29, 2019):

I've also seen some crashes on rendering special characters. Perhaps cmatrix is just a fancy way to make us render special characters?

@DHowett-MSFT commented on GitHub (Jul 29, 2019): I've also seen some crashes on rendering special characters. Perhaps cmatrix is just a fancy way to make us render special characters?
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@EFanZh commented on GitHub (Aug 4, 2019):

I noticed that cmatrix runs slowly in Windows Terminal comparing to Alacritty.

Try the following command:

cmatrix -u0

In Alacritty I can get a smooth animation, but in Windows Terminal, the animation seems slow.

@EFanZh commented on GitHub (Aug 4, 2019): I noticed that cmatrix runs slowly in Windows Terminal comparing to [Alacritty](https://github.com/jwilm/alacritty). Try the following command: cmatrix -u0 In Alacritty I can get a smooth animation, but in Windows Terminal, the animation seems slow.
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 13, 2019):

We believe this is #2375

@zadjii-msft commented on GitHub (Sep 13, 2019): We believe this is #2375
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@dkambersky commented on GitHub (Oct 24, 2019):

Fwiw I can't reproduce the slowdown on the 1910 preview release. Cmatrix appear to run normally now.

@dkambersky commented on GitHub (Oct 24, 2019): Fwiw I can't reproduce the slowdown on the 1910 preview release. Cmatrix appear to run normally now.
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Oct 24, 2019):

@dkambersky Thanks for the feedback! 1910 preview does include performance enhancement that's intended to make cmatrix great again.

@skyline75489 commented on GitHub (Oct 24, 2019): @dkambersky Thanks for the feedback! 1910 preview does include performance enhancement that's intended to make `cmatrix` great again.
claunia commented 2026-01-30 23:07:16 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Oct 24, 2019):

Largely, this issue should be fixed. With a higher resolution and smaller font, the rendering pressure will be higher. And the cmatrix lag will be more likely to appear. But overall CPU usage is significantly lower.

@skyline75489 commented on GitHub (Oct 24, 2019): Largely, this issue should be fixed. With a higher resolution and smaller font, the rendering pressure will be higher. And the `cmatrix` lag will be more likely to appear. But overall CPU usage is significantly lower.
claunia commented 2026-01-30 23:07:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 28, 2019):

I'm going to close this one based off the excellent work @skyline75489 committed for 0.6, and other changes in that release that should have mitigated this crash. For any other persistent perf issues, I'll direct conversation to #1064.

Thanks all!

@zadjii-msft commented on GitHub (Oct 28, 2019): I'm going to close this one based off the excellent work @skyline75489 committed for 0.6, and other changes in that release that should have mitigated this crash. For any other persistent perf issues, I'll direct conversation to #1064. Thanks all!
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 Issue-Bug Product-Terminal Resolution-Fix-Available Severity-Crash
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#2858
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?