Unresponsive / Won't accept input

[thecaligarmo]

Windows Terminal version

1.22.10731.0

Windows build number

10.0.26100.3775

Other Software

No response

Steps to reproduce

Not sure what happened/was changed, but this morning my terminal stopped accepting input every so often. (So not sure how to reproduce it). In essence what I noticed:

1. WSL was not responding to keyboard input, I thought it had crashed so closed it and reopened, with no succes.
2. I restarted my computer to see if a simple on/off cycle would fix it. At first it accepted when I typed ls, but then shortly after it stopped accepting input again.
3. I thought maybe it was due to lack of space (as it seemed to happen after I downloaded something), but this was not true:

aram:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
none            7.8G     0  7.8G   0% /usr/lib/modules/5.15.167.4-microsoft-standard-WSL2
none            7.8G  4.0K  7.8G   1% /mnt/wsl
drivers         1.9T  1.4T  513G  73% /usr/lib/wsl/drivers
/dev/sdc       1007G   86G  870G   9% /
none            7.8G   92K  7.8G   1% /mnt/wslg
none            7.8G     0  7.8G   0% /usr/lib/wsl/lib
rootfs          7.8G  2.4M  7.8G   1% /init
none            7.8G  996K  7.8G   1% /run
none            7.8G     0  7.8G   0% /run/lock
none            7.8G     0  7.8G   0% /run/shm
tmpfs           4.0M     0  4.0M   0% /sys/fs/cgroup
none            7.8G  1.1M  7.8G   1% /mnt/wslg/versions.txt
none            7.8G  1.1M  7.8G   1% /mnt/wslg/doc
C:\             1.9T  1.4T  513G  73% /mnt/c
tmpfs           7.8G  216K  7.8G   1% /run/qemu
snapfuse        128K  128K     0 100% /snap/bare/5
snapfuse         74M   74M     0 100% /snap/core22/1802
snapfuse        506M  506M     0 100% /snap/gnome-42-2204/176
snapfuse        517M  517M     0 100% /snap/gnome-42-2204/202
snapfuse         92M   92M     0 100% /snap/gtk-common-themes/1535
snapfuse         45M   45M     0 100% /snap/snapd/23545
snapfuse         45M   45M     0 100% /snap/snapd/23771
snapfuse        131M  131M     0 100% /snap/ubuntu-desktop-installer/1284
snapfuse        132M  132M     0 100% /snap/ubuntu-desktop-installer/1286
snapfuse         74M   74M     0 100% /snap/core22/1908

4. I opened command prompt to see if it was a wsl thing, but after one command, the command prompt stopped working as well.
5. After waiting a few minutes (5-10), the command prompt (and wsl) both started accepting input, but then less than 1 minute later it stopped accepting input again.
6. Just to double check it was an input problem and not an output problem, I started a terminal with htop running, and the output was constantly changing even though I was not able to input anything into any of the other prompts.

I'm not sure, but #18755 seems to be having similar problems (but maybe it's unrelated). I've tried adding a dump file, but not sure if it worked properly or not.

Expected Behavior

Smooth keyboard input.

Actual Behavior

Input stops being accepted every so often.

[thecaligarmo]

Some extra notes:

1. While this was happening, htop was not showing an increased memory or CPU usage. They were all fairly low.
2. I tried disabling every program that was running (except for opera and dropbox) and the issue was still persistent.
3. It seems to not always occur (for example: earlier it was happening after 1-2 commands, but now I've been able to run a few different commands without an issue.... [of course it starts working after I submit an issue 😅 ])
4. Finally, during this time I was still able to use VS Code's terminal without any issue.

[thecaligarmo]

PS I noticed that the file didn't upload for some reason. When I tried doing it again I get the following error: Failed to upload "WindowsTerminal.DMP" from Github. I'm not sure what the best way to upload a file is since github won't let me.

[DHowett]

Hey, this one is quite strange!

• Do you have anything anomalous in the Event Viewer?
• When you say "command prompt" do you mean inside Terminal or are you launching it in the "Windows Console Host"? I'm guessing the former, but just wanted to make sure.
• Have you changed the settings on the "Touch, Keyboard and Handwriting" service in services.msc/?

[thecaligarmo]

To Answer your questions.

1. I've not checked Event Viewer, but not really sure where to look inside of it directly.
2. By Command prompt I mean inside the terminal. As in, think of a normal linux terminal, and when I'm trying to type inside it, nothing happens.
3. I have not touched any settings in the services. When I use run to open services.msc, there's not even a "Touch, Keyboard and Handwriting" option in there...

Note: I realised I can't upload the file because it's a .dmp file and according to github, I can't upload .dmp files: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files

I haven't been using the terminal as much over the past few days, so have not seen if this is still happening or if it "magically fixed itself" as things sometimes like to do.

[thecaligarmo]

I'm not sure if this helps, but it started doing it again this morning, so I checked Event Viewer to see if there's anything showing up. Here's some images of what I'm seeing. Coincidentally, the timing seems to match with my previous instance as well (and a couple of other times, but I probably didn't notice those)

Errors:

Warnings:

[thecaligarmo]

Is there any update on this? The issue is still persistent. Here are my current version info:

Windows Terminal version 1.22.11141.0

Windows build number 10.0.26100.4061

[lhecker]

We have several theories why this may happen. Previously we had hangs like this due to driver issues, incompatibilities with AV vendors, etc. Could you try to record an ETW trace for us? Here are the instructions: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace

The trace will contain every input and output of your terminal so make sure it doesn't contain any sensitive data. But the good news is that you can leave the trace running for long periods of time if needed. It'll hopefully show if your input even goes through the terminal into the console application.

FWIW the error messages you're seeing in Event Viewer don't look too good either. Getting that addressed (or reinstalling Windows) may be useful in any case.

[thecaligarmo]

Sounds good. I'll try and do a ETW trace if I see it happen again. I haven't noticed it happen recently, but mostly because I've been away from my computer for the past few weeks. I'll also make sure no sensitive data gets logged.

Yeah, I'm not sure what the event viewer stuff is. I had bought my laptop from Alienware and every time I mentioned problems they just said "our diagnostic isn't showing anything" and so refused to help. I'll need to see what I can do once I have backup computer. Thanks for the advice.