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

WSL 2 freezes #10999

Closed
1 of 2 tasks
marchello2000 opened this issue Jan 8, 2024 · 7 comments
Closed
1 of 2 tasks

WSL 2 freezes #10999

marchello2000 opened this issue Jan 8, 2024 · 7 comments

Comments

@marchello2000
Copy link

Windows Version

Microsoft Windows [Version 10.0.22621.2861]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 22.04.3

Other Software

IntelliJ

Repro Steps

Don't have reliable repro steps, but every once in a while my WSL will just freeze and the VmmmemWSL process will not use up much CPU but will peg the disk and use tons of RAM.

Usually happens when I run gradle.

Sometimes, in this state, even wsl shutdown doesn't work:

> wsl shutdown

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error code: Wsl/Service/0x8007274c

Usually need to reboot Windows to get things working again. Logs attached.

Happens once in a while (~1/wk)

Expected Behavior

No freezing

Actual Behavior

freezes

Diagnostic Logs

WslLogs-2024-01-08_14-47-40.zip

Copy link

github-actions bot commented Jan 8, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 10, 2024

@marchello2000: by "wsl shutdown", do you mean "wsl --shutdown" ?

Regarding the hang, looking at the logs, I see a lot of plan9 traffic but that's one enough to root cause.

Next time this happens, can you share a /dump of the WSL processes ?

Copy link
Contributor

Hello! Could you please provide logs and process dumps to help us better diagnose your issue?

To collect WSL logs and dumps, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1 -Dump

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 10, 2024

Also, another thing: I see that you have swap disabled. That can potentially cause a hang if WSL runs out of memory. Can you try enabling swap again in .wslconfig ?

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

@nicoborghi
Copy link

Same for me. My workaround is to kill the process in (admin) PowerShell and then restart WSL:

taskkill /f /im wslservice.exe

@vmnit
Copy link

vmnit commented Feb 10, 2024

Same here. Facing keyboard input freeze after every one command.
Even facing issue with the same frequent freeze while writing in the nvim.

wsl shutdown seems to be overkill. It seems that some service is getting high priority over the keyboard input, and that is causing these frequent freezes.
Not sure, if there is a setting which can help here.

If anyone has any solution, please share.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants