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

frequently experience unresposive situation #23160

New Issue
Closed
opened 2026-01-31 08:34:01 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 08:34:01 +00:00
Owner
Copy Link

Originally created by @Mohan-077 on GitHub (Apr 16, 2025).

I frequently encounter situations where Windows Terminal becomes unresponsive. This typically happens during regular usage—like switching between tabs or executing commands. The UI freezes, and I’m unable to type or interact with the terminal until I force close and reopen it.
Steps to Reproduce

Open Windows Terminal

Start a session (e.g., PowerShell or WSL)

Perform common tasks like running commands or switching tabs

Terminal becomes unresponsive after a short time

Expected Behavior

Terminal should remain responsive during normal use.
Actual Behavior

Terminal occasionally freezes and stops responding, requiring a force close.

Originally created by @Mohan-077 on GitHub (Apr 16, 2025). I frequently encounter situations where Windows Terminal becomes unresponsive. This typically happens during regular usage—like switching between tabs or executing commands. The UI freezes, and I’m unable to type or interact with the terminal until I force close and reopen it. Steps to Reproduce Open Windows Terminal Start a session (e.g., PowerShell or WSL) Perform common tasks like running commands or switching tabs Terminal becomes unresponsive after a short time Expected Behavior Terminal should remain responsive during normal use. Actual Behavior Terminal occasionally freezes and stops responding, requiring a force close.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 08:34:01 +00:00
claunia commented 2026-01-31 08:34:04 +00:00
Author
Owner
Copy Link

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

Thanks for the report! Can you help us out by capturing a dump file/?

@DHowett commented on GitHub (Apr 16, 2025): Thanks for the report! Can you help us out by [capturing a dump file](https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-and-sending-dumps)/?
claunia commented 2026-01-31 08:34:04 +00:00
Author
Owner
Copy Link

@urucchi commented on GitHub (Apr 17, 2025):

I've noticed this too, only recently (within the last couple weeks). I'm unsure if it's due to an update or not, but I did try installing v1.23.10732.0 preview and the issue persisted. It's very consistent for me - I can spam keys and within a few seconds it will look like the terminal has frozen. No keyboard or mouse input appears to do anything, however I know my inputs are actually working because I can get the warning for pasting content with newlines to show up, and also after waiting a few minutes, everything shows up, including whatever I mashed while it seemed frozen. This happens for WSL, Command, and Powershell. Since things eventually "come back" after some time, I assume this is a rendering issue.

I sent a dump to @zadjii-msft but I'm happy to provide any more info since I can easily repro this.

@urucchi commented on GitHub (Apr 17, 2025): I've noticed this too, only recently (within the last couple weeks). I'm unsure if it's due to an update or not, but I did try installing v1.23.10732.0 preview and the issue persisted. It's very consistent for me - I can spam keys and within a few seconds it will look like the terminal has frozen. No keyboard or mouse input appears to do anything, however I know my inputs are actually working because I can get the warning for pasting content with newlines to show up, and also after waiting a few minutes, everything shows up, including whatever I mashed while it seemed frozen. This happens for WSL, Command, and Powershell. Since things eventually "come back" after some time, I assume this is a rendering issue. I sent a dump to @zadjii-msft but I'm happy to provide any more info since I can easily repro this.
claunia commented 2026-01-31 08:34:05 +00:00
Author
Owner
Copy Link

@Chris-Irving commented on GitHub (Apr 23, 2025):

Commenting so this is not auto-closed. This input lag or latency is still an issue. This was previously fixed or improved in v1.19 per GitHub Issue 5590. This problem is back in v1.22 and potentially others.

Similar reports:

@Chris-Irving commented on GitHub (Apr 23, 2025): Commenting so this is not auto-closed. This input lag or latency is still an issue. This was previously fixed or improved in v1.19 per [GitHub Issue 5590](https://github.com/microsoft/terminal/issues/5590). This problem is back in v1.22 and potentially others. Similar reports: * https://github.com/microsoft/terminal/issues/18755 * https://github.com/microsoft/terminal/issues/18790
claunia commented 2026-01-31 08:34:05 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 23, 2025):

Given that there seems to be a strong resurgence of input bugs being filed on us, I have great hopes that #18816 will fix at least most of them.

@lhecker commented on GitHub (Apr 23, 2025): Given that there seems to be a strong resurgence of input bugs being filed on us, I have great hopes that #18816 will fix at least most of them.
claunia commented 2026-01-31 08:34:05 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 24, 2025):

You can help us (me?) test my fix by running our Canary version: https://aka.ms/terminal-canary-installer
Please let us know if the issue still occurs in that version.

@lhecker commented on GitHub (Apr 24, 2025): You can help us (me?) test my fix by running our Canary version: https://aka.ms/terminal-canary-installer Please let us know if the issue still occurs in that version.
claunia commented 2026-01-31 08:34:06 +00:00
Author
Owner
Copy Link

@willgleich commented on GitHub (Apr 25, 2025):

i have seemingly identical symptoms to this. I have confirmed it happens on all terminals, cmd, WSL or Powershell. After a short amount of time the tab will "freeze" and I'm unable to register any input. I just tried the canary release you linked 1.24.1141.0 and unfortunately it froze right away on PowerShell tab when trying to do simple ls and file movement commands.

Also happening on my general release 1.22.10731.0

Any workarounds? Would a downgrade stabilize things? Happy to provide more info since I also have a consistent reproduction.

@willgleich commented on GitHub (Apr 25, 2025): i have seemingly identical symptoms to this. I have confirmed it happens on all terminals, cmd, WSL or Powershell. After a short amount of time the tab will "freeze" and I'm unable to register any input. I just tried the canary release you linked 1.24.1141.0 and unfortunately it froze right away on PowerShell tab when trying to do simple ls and file movement commands. Also happening on my general release 1.22.10731.0 Any workarounds? Would a downgrade stabilize things? Happy to provide more info since I also have a consistent reproduction.
claunia commented 2026-01-31 08:34:06 +00:00
Author
Owner
Copy Link

@urucchi commented on GitHub (Apr 25, 2025):

Unlike @willgleich the canary build seems to have fixed it for me. I've tried reproducing it on WSL and powershell and it doesn't seem to be happening anymore. My build says it is version 1.24.1141.0

@urucchi commented on GitHub (Apr 25, 2025): Unlike @willgleich the canary build seems to have fixed it for me. I've tried reproducing it on WSL and powershell and it doesn't seem to be happening anymore. My build says it is version 1.24.1141.0
claunia commented 2026-01-31 08:34:07 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 25, 2025):

Would a downgrade stabilize things?

If you remain on that version, yes. But otherwise, we need leads to be able to fix it, as otherwise future versions will continue to have this issue. You can help us by capturing a heap dump once it occurs (the more we get, the better): https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-with-task-manager
Then simply send it to one of the team members via mail. My mail is <github username>@microsoft.com.

@lhecker commented on GitHub (Apr 25, 2025): > Would a downgrade stabilize things? If you remain on that version, yes. But otherwise, we need leads to be able to fix it, as otherwise future versions will continue to have this issue. You can help us by capturing a heap dump once it occurs (the more we get, the better): https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-with-task-manager Then simply send it to one of the team members via mail. My mail is `<github username>@microsoft.com`.
claunia commented 2026-01-31 08:34:07 +00:00
Author
Owner
Copy Link

@willgleich commented on GitHub (Apr 29, 2025):

Bump to remove stale, sent memory dumps to @lhecker

@willgleich commented on GitHub (Apr 29, 2025): Bump to remove stale, sent memory dumps to @lhecker
claunia commented 2026-01-31 08:34:07 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 30, 2025):

@willgleich Can you check where you sent it to and whether the delivery was successful? I can't seem to find a mail under my work (@microsoft.com) nor personal address (@hecker.io). (I made sure to check the junk folders. 😅)

@lhecker commented on GitHub (Apr 30, 2025): @willgleich Can you check where you sent it to and whether the delivery was successful? I can't seem to find a mail under my work (@microsoft.com) nor personal address (@hecker.io). (I made sure to check the junk folders. 😅)
claunia commented 2026-01-31 08:34:08 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 12, 2025):

@willgleich I had a chance now to look at your dumps. One of them didn't show anything interesting, the other one however showed that the renderer was stuck inside the Nvidia driver. I also noticed you're running on build 26100. To you and everyone else:

If you have an Nvidia GPU, please make sure you aren't running into this issue: https://github.com/microsoft/terminal/issues/18040
To fix it, update Windows. If you can't update Windows do this https://github.com/microsoft/terminal/issues/18040#issuecomment-2466734253 or this https://github.com/microsoft/terminal/issues/18040#issuecomment-2494530655 or both.

@lhecker commented on GitHub (May 12, 2025): @willgleich I had a chance now to look at your dumps. One of them didn't show anything interesting, the other one however showed that the renderer was stuck inside the Nvidia driver. I also noticed you're running on build 26100. To you and everyone else: If you have an Nvidia GPU, please make sure you aren't running into this issue: https://github.com/microsoft/terminal/issues/18040 To fix it, update Windows. If you can't update Windows do this https://github.com/microsoft/terminal/issues/18040#issuecomment-2466734253 or this https://github.com/microsoft/terminal/issues/18040#issuecomment-2494530655 or both.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage
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#23160
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?