Slow performance and higher CPU usage #12710

Closed
opened 2026-01-31 03:22:44 +00:00 by claunia · 6 comments
Owner

Originally created by @jr-lillard on GitHub (Feb 24, 2021).

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.804]
Windows Terminal version (if applicable): 1.5.10411.0

Any other software?

Steps to reproduce

Open up a WSL terminal and let this run for a day: while true; do echo -e -n "`date`\r"; sleep 1; done

Expected behavior

The current date / time should display and then get overwritten every second.

Actual behavior

The date / time is displayed and gets overwritten every second. After doing this for 24 hours (maybe less), the terminal instance becomes very slow and uses up more CPU than necessary. Split the window and typing in the other pane is slowed down a bit. Open another tab and typing is slowed down. Closing the window is the only way to resolve the issue so far.

The command above is not the actually command I'm doing. I'm actually running an rsync in the while loop. I'm using \r as I don't need the scroll back buffer for this command. I only need the current status. My theory is that even though \r clears the line, it's getting recorded in the buffer. Over time the buffer gets so big everything slows down. I'm trying the same command with with \n now to see if it behaves the same. I will report back my findings in a day or so.

Originally created by @jr-lillard on GitHub (Feb 24, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Microsoft Windows [Version 10.0.19042.804] Windows Terminal version (if applicable): 1.5.10411.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Open up a WSL terminal and let this run for a day: while true; do echo -e -n "\`date\`\r"; sleep 1; done # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The current date / time should display and then get overwritten every second. # Actual behavior <!-- What's actually happening? --> The date / time is displayed and gets overwritten every second. After doing this for 24 hours (maybe less), the terminal instance becomes very slow and uses up more CPU than necessary. Split the window and typing in the other pane is slowed down a bit. Open another tab and typing is slowed down. Closing the window is the only way to resolve the issue so far. The command above is not the actually command I'm doing. I'm actually running an rsync in the while loop. I'm using \r as I don't need the scroll back buffer for this command. I only need the current status. My theory is that even though \r clears the line, it's getting recorded in the buffer. Over time the buffer gets so big everything slows down. I'm trying the same command with with \n now to see if it behaves the same. I will report back my findings in a day or so.
claunia added the Resolution-Duplicate label 2026-01-31 03:22:44 +00:00
Author
Owner

@WSLUser commented on GitHub (Feb 24, 2021):

Are you using WSL2? Have you tried this without Windows Terminal and get different results?

@WSLUser commented on GitHub (Feb 24, 2021): Are you using WSL2? Have you tried this without Windows Terminal and get different results?
Author
Owner

@jr-lillard commented on GitHub (Feb 25, 2021):

I am not running WSL2. I have not tried this without Windows Terminal. It's been almost 24 hours and the same command using \n instead of \r is not causing any problems.

@jr-lillard commented on GitHub (Feb 25, 2021): I am not running WSL2. I have not tried this without Windows Terminal. It's been almost 24 hours and the same command using \n instead of \r is not causing any problems.
Author
Owner

@ssc-wiit commented on GitHub (Feb 25, 2021):

I have a similar issue with WSL2. Usually I let Windows Terminal run for weeks with multiple different tabs, some of which accumulate a long history of commands and shell output.

A fresh instance of "WindowsTerminal.exe" will sit at 0% CPU while idle, but after a week of usage it now sits at 4% CPU idle. The highest I observed via TaskManager before restarting the terminal was a constant 10% CPU while all tabs were sitting completely idle on a shell prompt.

Opening a fresh tab and then closing all other old tabs does NOT lower the CPU usage. I have to completely close and re-open the Windows Terminal.

@ssc-wiit commented on GitHub (Feb 25, 2021): I have a similar issue with WSL2. Usually I let Windows Terminal run for weeks with multiple different tabs, some of which accumulate a long history of commands and shell output. A fresh instance of "WindowsTerminal.exe" will sit at 0% CPU while idle, but after a week of usage it now sits at 4% CPU idle. The highest I observed via TaskManager before restarting the terminal was a constant 10% CPU while all tabs were sitting completely idle on a shell prompt. Opening a fresh tab and then closing all other old tabs does NOT lower the CPU usage. I have to completely close and re-open the Windows Terminal.
Author
Owner

@ssc-wiit commented on GitHub (Feb 25, 2021):

At least for my case it seems to be related to https://github.com/microsoft/terminal/issues/7710

@ssc-wiit commented on GitHub (Feb 25, 2021): At least for my case it seems to be related to https://github.com/microsoft/terminal/issues/7710
Author
Owner

@zadjii-msft commented on GitHub (Feb 25, 2021):

Yea, this sounds exactly like #7710. We don't really have any idea what causes it. #9006 is similar too. The absolute worst part of this is how inconsistent the repro is - I had this happen to me once, but never again on any subsequent terminals.

For now, I'm gonna close this as a /dupe of #7710 to try and keep the discussion contained. Thanks!

@zadjii-msft commented on GitHub (Feb 25, 2021): Yea, this sounds exactly like #7710. We don't really have any idea what causes it. #9006 is similar too. The absolute worst part of this is how inconsistent the repro is - I had this happen to me once, but never again on any subsequent terminals. For now, I'm gonna close this as a /dupe of #7710 to try and keep the discussion contained. Thanks!
Author
Owner

@ghost commented on GitHub (Feb 25, 2021):

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 (Feb 25, 2021): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12710