Spinner grinds mstsc rdp sessions to a halt #23447

Closed
opened 2026-01-31 08:42:30 +00:00 by claunia · 4 comments
Owner

Originally created by @AdmiralSnyder on GitHub (Jul 14, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.4652

Other Software

i' m using two nested mstsc sessions for work and did a winget update --all just now.
and suddenly, my cursor would only hop over the screen. something ground the responsiveness of the system to a halt (i'm using quite a slow machine for some reason, but that doesn't really matter) turns out, it's the mstsc, turns out it's the windows terminal... and it's the spinner - both in tabs and e.g. in the about page when it's checking for updates. it's firing redraw calls like a mad person and apparently mstsc is very keen on forwarding those.
can you please detect if you're in a rdp session and reduce that eagerness a little bit? - or maybe add a setting... i don't want to disable animations, but ... a lowFPS setting might be fine.

just for context: i had a similar problem with VS deciding to have a full-screen-width "i'm" busy - bar at some point, grinding everything to a halt, too. i suppose that issue still is in devcom limbo...

thanks a lot :-)

Steps to reproduce

have a slow pc (and maybe a somewhat bad internet connection), rdp onto a windows machine (maybe a second layer is needed to surface the problem, no idea), open a windows terminal there, move your mouse to make sure the cursor is moving nicely, then go to the about page of the windows terminal and observe stuttering while it's checking for updates, showing the spinner

Expected Behavior

no huge redraw spikes for animations

Actual Behavior

apparently mstsc wants to redraw the terminal (or the animating parts) a lot, grinding everything to a halt

Originally created by @AdmiralSnyder on GitHub (Jul 14, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.26100.4652 ### Other Software i' m using two nested mstsc sessions for work and did a winget update --all just now. and suddenly, my cursor would only hop over the screen. _something_ ground the responsiveness of the system to a halt (i'm using quite a slow machine for some reason, but that doesn't really matter) turns out, it's the mstsc, turns out it's the windows terminal... and it's the spinner - both in tabs and e.g. in the about page when it's checking for updates. it's firing redraw calls like a mad person and apparently mstsc is very keen on forwarding those. can you please detect if you're in a rdp session and reduce that eagerness a little bit? - or maybe add a setting... i don't want to disable animations, but ... a lowFPS setting might be fine. just for context: i had a similar problem with VS deciding to have a full-screen-width "i'm" busy - bar at some point, grinding everything to a halt, too. i suppose _that_ issue still is in devcom limbo... thanks a lot :-) ### Steps to reproduce have a slow pc (and maybe a somewhat bad internet connection), rdp onto a windows machine (maybe a second layer is needed to surface the problem, no idea), open a windows terminal there, move your mouse to make sure the cursor is moving nicely, then go to the about page of the windows terminal and observe stuttering while it's checking for updates, showing the spinner ### Expected Behavior no huge redraw spikes for animations ### Actual Behavior apparently mstsc wants to redraw the terminal (or the animating parts) a lot, grinding everything to a halt
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:42:30 +00:00
Author
Owner

@AdmiralSnyder commented on GitHub (Jul 14, 2025):

Image this is the spinner i mean, btw. (the one next to "Checking for updates" the same bad behaviour occurs when a tab's icon is showing the "i'm busy" circle, too, and for a lesser degree, when it's displaying progress (i.e. slowly filling the circle)
@AdmiralSnyder commented on GitHub (Jul 14, 2025): <img width="334" height="141" alt="Image" src="https://github.com/user-attachments/assets/ed90ce09-c48f-4339-8231-f24223b85932" /> this is the spinner i mean, btw. (the one next to "Checking for updates" the same bad behaviour occurs when a tab's icon is showing the "i'm busy" circle, too, and for a lesser degree, when it's displaying progress (i.e. slowly filling the circle)
Author
Owner

@DHowett commented on GitHub (Jul 16, 2025):

You know, that's really surprising! I wonder if other users of the WinUI indeterminate progress ring cause the same slowdown? It's not something that we can really fix on our end, but maybe an issue on their repo would help?

As for the ones we can control (CLI application-requested progress rings), I'm going to call this a duplicate of #19121 (which may not currently have the right title but we'll fix)

@DHowett commented on GitHub (Jul 16, 2025): You know, that's really surprising! I wonder if other users of the WinUI indeterminate progress ring cause the same slowdown? It's not something that we can really _fix_ on our end, but maybe an [issue on their repo](https://github.com/microsoft/microsoft-ui-xaml/issues/new) would help? As for the ones we _can_ control (CLI application-requested progress rings), I'm going to call this a duplicate of #19121 (which may not currently have the right title but we'll fix)
Author
Owner

@DHowett commented on GitHub (Jul 16, 2025):

By chance, is your RDP session running in one of the modes that is more performant on slower connections?

Image Image
@DHowett commented on GitHub (Jul 16, 2025): By chance, is your RDP session running in one of the modes that is more performant on slower connections? <img width="586" height="363" alt="Image" src="https://github.com/user-attachments/assets/99859886-572a-40f1-a6b0-b80fb5588096" /> <img width="543" height="312" alt="Image" src="https://github.com/user-attachments/assets/ccca16bb-d78b-4287-a4d4-e81ac6d31423" />
Author
Owner

@AdmiralSnyder commented on GitHub (Jul 16, 2025):

no, i didn't fiddle with those settings, maybe something there helps - good idea. i suspect the gpu(s) to be another reason for the problem, though - it's a thin client... if only there were some diagnostics mstsc would provide :-)

@AdmiralSnyder commented on GitHub (Jul 16, 2025): no, i didn't fiddle with those settings, maybe something there helps - good idea. i suspect the gpu(s) to be another reason for the problem, though - it's a thin client... if only there were _some_ diagnostics mstsc would provide :-)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23447