search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.33k stars 814 forks source link

WSL Freezing 0x8007274c #9832

Open andersonams opened 1 year ago

andersonams commented 1 year ago

Windows Version

10.0.22621.1413

WSL Version

1.1.3.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.90.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04.1 LTS

Other Software

Versão do WSL: 1.1.3.0
Versão do kernel: 5.15.90.1
Versão do WSLg: 1.0.49
Versão do MSRDC: 1.2.3770
Versão do Direct3D: 1.608.2-61064218
Versão do DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows versão: 10.0.22621.1413

Repro Steps

Every that I set up my development applications (such as Docker, PhpStorm, WebStorm, etc), it starts to happen repeatedly throughout the day.

Additional Information:

I started to experience it since from Windows 10 22H2 update. After a while, I did a fresh Windows 11 install, and the behavior is still happening.

image

Expected Behavior

Terminals and apps work without hangs.

Actual Behavior

To be able to continue to work:

Diagnostic Logs

No response

OneBlue commented 1 year ago

/logs

microsoft-github-policy-service[bot] commented 1 year ago

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, 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

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!

ttuna commented 1 year ago

I had the same issue when running a amazonlinux container in WSL. As long as the container was up, i was not able to open a second WSL instance in Windows.

andersonams commented 1 year ago

WslLogs-2023-03-31_14-26-43.zip

OneBlue commented 1 year ago

Thanks @andersonams. Looking at the logs, it looks like the issue is that WSL is out of memory.

Does increasing wsl2.memory to let's say 8GB help ?

andersonams commented 1 year ago

Thanks @andersonams. Looking at the logs, it looks like the issue is that WSL is out of memory.

Does increasing wsl2.memory to let's say 8GB help ?

So, after the fresh Windows 11 install, I tried the "free memory" mode, with no explicit configuration on the .wslconfig before and I was seeing the same behavior. Same as well when I put 8GB.

With no explicit configuration, the VmmemWSL process almost hits 8GB of usage (the PC has 16GB total), but with the same behavior that I described.

While I was trying to found a solution through internet, I saw some hints to put guiApplications=false into .wslconfig. But, it did not help too much. Only the high CPU usage of VmmemWSL was mitigated.

GuidoKiu commented 6 months ago

Docker Command Error in WSL

When running the command docker scout quickview in Windows Subsystem for Linux (WSL), I encountered the following error: 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 Press any key to continue...

[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.

WslLogs-2024-03-14_21-38-38.zip

MouraVocal commented 5 months ago

This is happening to me constantly lately. since I started working on a project where I need to run front-end and back-end servers at the same time, and one docker container running a postgreSQL and I'm coding with VsCode, my machine got 16Gb RAM, and I'm not using .wslconfig, but I read the WSL docs and it tells me that the default RAM is 50% windows RAM, so I think maybe the problem is not a RAM problem, maybe something with vscode and/or some plugin.

MaverickMartyn commented 4 months ago

I'm having the same issue, trying to run a frontend in WSL, while the Windows based backend runs some docker containers.

xmakina commented 3 months ago

Continuing to be a problem, after turning my computer on and opening the Ubuntu app, I get

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
Press any key to continue...

So far, the only workaround I have found is to open a cmd prompt and run wsl --shutdown and restart WSL

MaverickMartyn commented 3 months ago

I had forgotten about this thread, but for what it's worth, I think I fixed it by reinstalling WSL and some related tools.

shuffle2 commented 2 months ago

I also get this sporadically. This issue report mentioned vscode as a contributing factor, and I was able to confirm that killing the vscode instance which had been open for a long time (with C++ intellisense plugin) which had a wsl2 remote directory open, fixed the problem. Not sure what the underlying issue is, though.

MouraVocal commented 2 months ago

I tried giving more memory to WSL and this worked for me, just create a file named .wslconfig on your %UserProfile% folder on windows and set this config

[wsl2]
memory=10GB

restart WSL and maybe this works for you too.

Durga1prasad commented 1 month ago

WslLogs-2024-08-30_16-32-58.zip