frequently experience unresposive situation

[Mohan-077]

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.

[DHowett]

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

[urucchi]

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.

[Chris-Irving]

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:

• Frequently experiencing unresponsive situations #18755
• Unresponsive / Won't accept input #18790

[lhecker]

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]

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.

[willgleich]

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.

[urucchi]

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

[lhecker]

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.

[willgleich]

Bump to remove stale, sent memory dumps to @lhecker

[lhecker]

@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]

@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: #18040
To fix it, update Windows. If you can't update Windows do this #18040 (comment) or this #18040 (comment) or both.