Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal hangs constantly while running WSL 2 #17096

Closed
lumbytyci opened this issue Apr 21, 2024 · 4 comments
Closed

Terminal hangs constantly while running WSL 2 #17096

lumbytyci opened this issue Apr 21, 2024 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@lumbytyci
Copy link

lumbytyci commented Apr 21, 2024

Windows Terminal version

1.19.10821.0

Windows build number

10.0.22631.3447

Other Software

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3447

Steps to reproduce

  1. Open Windows Terminal
  2. Launch WSL 2 (I'm running Debian)
  3. Do some work, usually happens after I save and quit from vim or any console application that has some kind of CLI
  4. Windows Terminal will hang (not freeze, there is no Program Not Responding message).

This will happen every few minutes or so. When this happens I have to wait ~30 seconds for the terminal to become responsive. Once responding, all of the previously buffered inputs will flush into the terminal.

Recently I discovered a way to immediately make the terminal responsive once it starts to hang. I do this by sending a SIGINT/Ctrl + C which immediately registers in the terminal (^C) and afterwards zooming in or out (ctrl +/-) - this seems to do the trick.

I'm directing this issue to this repository as opposed to the WSL repository since this issue is not reproducible with other terminal applications.
I can observe this identical issue in both of my devices running Windows 11.

Expected Behavior

Windows Terminal should not hang

Actual Behavior

Windows Terminal hangs

@lumbytyci lumbytyci added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 21, 2024

This comment was marked as off-topic.

@zadjii-msft
Copy link
Member

Any chance you can narrow down the repro steps at all? A specific set of commands you're running to make this happen would be helpful, or maybe more info about your vim setup? I know there's at least one other thread around here where IIRC, there's some vim plugin that seems to cause the Terminal to hang.

Another thing that may be helpful to know - does this repro with the vintage console host, conhost.exe/?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Apr 23, 2024
@lumbytyci
Copy link
Author

Any chance you can narrow down the repro steps at all? A specific set of commands you're running to make this happen would be helpful, or maybe more info about your vim setup? I know there's at least one other thread around here where IIRC, there's some vim plugin that seems to cause the Terminal to hang.

Another thing that may be helpful to know - does this repro with the vintage console host, conhost.exe/?

I'll do my best to find an exact scenario to reproduce this issue. Is the terminal storing some kind of logs which I could extract and share here?

Funny enough, just as I read your remark I opened the legacy command line application conhost.exe and launched WSL 2 by typing debian and as soon as it launched - it immediately froze. In contrast with windows terminal, zooming didn't fix the problem here. I should note that I have neofetch configured to run in this device once I launch the terminal.

This makes me wonder whether the problem is actually with the windows terminal at all. I will try to mess around and will close the issue if nothing interesting is found.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Apr 23, 2024
@carlos-zamora carlos-zamora added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Apr 25, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Apr 29, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

3 participants