-
Notifications
You must be signed in to change notification settings - Fork 823
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
Windows commands inside WSL hang forever #7883
Comments
While shutting down WSL doesn't fix it, rebooting the PC does. |
Interesting, we will probably need the /logs from the Windows side. Coud you please share those? |
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
I can confirm that I noticed the same issue. Quiet strange behavior, the first one or two times calling and windows executable works like a charm. Afterwards the behavior described by @siferati kicks in and only rebooting the system fixes it for now (did not try to dig deeper). @benhillis if you could provide an email where I could send the logs (recorded with: |
The logs can be attached here or in Feedback Hub as explained here https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs |
I've read that but did recorded it manually. Therefore I ask for an email as @craigloewen-msft did provide such email earlier on in some networking related issue. |
windows logs: logs.zip Sorry they're so long... I still haven't found a way to reliably trigger the issue, so I had to do random stuff for 5min until it eventually happened. I stopped recording once the problem occurred, so the relevant logs should be the most recent ones. Edit: replaced logs with shorter ones |
Some more info I found about the issue: When this issue happens, if I run windows commands (e.g. |
@siferati by any chance you're using |
I'm not using any of those tools AFAIK. The only thing I changed about launching wsl is running the docker daemon as described in https://docs.microsoft.com/en-us/windows/wsl/wsl-config#boot-settings |
I've found #7754 which sounds exactly like this issue. Maybe it's a good idea to mark this as duplicate. |
This happens to me daily when I try to launch VS Code using |
Thanks for the logs, I'll start looking at this. |
@benhillis would be awesome if you are able to reproduce and fix. Would such a fix get spread via a Microsoft Store WSL package update? For me the loss of interoperability happened for both the non-store and the latest store version. What happens is that my PHPStorm loses all Git functionality. The file I/O then stays ok, so PHPStorm still alows me to make edits. Restarting PHPStorm to see if Git interactions becomes available then crashes the entire IDE. When I/O interoperability is lost, I am unable to navigate to the mount from Explorer, nor am I able to start a new terminal and log into wsl by running the Found out that non-store wsl versions can solely update the kernel from the command line without upgrading to the store version by running |
Hitting this one daily running |
This behaviour was previously also filed, discussed but not yet remedied over at #7754 The work-around is to uninstall the store-version of WSL and revert to the "system" version. P.S. I see that @tobiaskohlbau already noted the prior issue. :) |
This workaround is not confirmed to work for everyone, myself included. |
@DHowett this is the one |
Thanks to everyone who submitted logs. We've made some progress on the issue, but we need more diagnostics to root cause it. Instructions once you have a repro (elevated command prompt):
Then using the task manager, check if the process is actually running on the Windows side, if it is, dump it (under the 'details tab', right click, then 'create dump file'). Do the same for all conhost.exe processes running on the machine. Then reply to this issue with |
@OneBlue your command has a typo: the curl should be done to a file named Terminal.wprp I wasn't able to record the logs, when I run the command I get I was trying to run notepad.exe but it did not show in the task manager. I uploaded the dumps from conhost to gdrive (too big to upload here). WSL: 0.51.2.0 |
Thanks @siferati. Fixed the typo :). Interesting, did Terminal.wprp get downloaded correctly ? If the process isn't created at all the logs would be what we need. |
Managed to fix the encoding error by replacing |
I've also started experiencing this issue in the last week. Seems to also be related to web servers running in WSL not responding to requests. WSL version: 0.51.2.0 |
New WSL version was released! https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-5.10.93.2 Would the following release notes that were included possibly relate to fixes for this bug?
|
Update: we're still actively investigating this issue. We know that the problem is between the Plan9 client on the host and the server that runs in WSL2, but we don't know what triggers this 'stuck' state yet. I'll update this issue when we'll have more info. |
You need to install https://www.microsoft.com/store/productId/9P9TQF7MRM4R which will then install the version, @OneBlue mentioned. Been running for a couple of hours now and I had no issues so far. |
Hi All! Thanks a lot for the fixes landed. With the new released version, would there be a preferred way to access the distros filesystems between |
Fyi, i had the windows wsl feature enabled as work around until fix for this came out. After announcement above i reinstalled the windows store wsl preview app then unchecked/removed the windows wsl feature and then rebooted. After that the
Also noticed that wsl preview store app, vs windows wsl feature install option honors windows host mouse button settings in wslg xclient/xserver gui app sessions. For example if you have swapped left and right mouse bottoms in windows host they will be swapped as well in wslg xclient/xserver gui app sessions which is nice level of integration. Also am finding my wsl linux distro wslg supported edge and chrome browser sessions are not hanging sporadically as they did with the windows wsl feature based install. |
When will non-preview WSL update? Will we be able to update using wsl --update? |
It seems that it crashes Jetbrains IDE again: A fatal error has been detected by the Java Runtime Environment:EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffda01badc0, pid=7192, tid=9236JRE version: OpenJDK Runtime Environment JBR-11.0.14.1.1-1751.46-jcef (11.0.14.1+1) (build 11.0.14.1+1-b1751.46)Java VM: OpenJDK 64-Bit Server VM JBR-11.0.14.1.1-1751.46-jcef (11.0.14.1+1-b1751.46, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)Problematic frame:V [jvm.dll+0x24adc0]` |
When the p9rdr.sys bug‘s fix ship to windows update? The bug still reproduce but very few times after I upgrade WSL from msstore. |
I updated to the latest version but it stills hangs every time I open a 2nd big project in PHPStorm with both project files located in \wsl$\Ubuntu\home\alex.... I am not trying to disable phpcs Inspection, which also located inside \wsl$. Furthermore, I think that it created numerous temporary files and seems better. I don't know if this is a wsl, jetbrains or a phpcs bug. It's not even possible to do wsl --shutdown now. My windows hang for minutes and new ubuntu cli don't respond. Please let me know what log files would help you |
@alexbogias Why do you think it's related to this issue? I don't see any indication in your posts that it is. Have you tried reaching out to JetBrains support? I see you commented under https://youtrack.jetbrains.com/issue/IDEA-276250, but hadn't even said if you did try the workaround mentioned there or not... And that issue seems to be an altogether different one than this one, despite some people mixing the two together in the comments... |
Phpstorm acts differently now with the latest wsl update, thats why. I think its more than one bug to be honest. And yes it looks like there are also jetbrains bug related :( |
@alexbogias Doesn't that, on the contrary, mean, that your problems are no longer related to this issue?
Yes, your problems are/were likely caused by multiple bugs jumbled together. But have you actually read through the whole https://youtrack.jetbrains.com/issue/IDEA-276250 issue and its comments where you posted? There are clear workarounds mentioned that most likely work for your problems too. And even though there probably is another WSL issue involved, it's not related to this particular WSL issue, but something along the lines of #7252... One day, I hope the projects that first instigated users to just use the issue tracker in place of a regular user group will go down in history books for the slippery slope they put all of us on... |
I am not really sure if that matters, but after uninstalling both WSL preview and WSLg preview from "add & remove programs (settings)" and did a wsl --update again, everything works more stable :S |
默认分发: Ubuntu @OneBlue I reproduced this problem on a new version, is it only fixed on 0.58.0 |
When is this going to be fixed? There's a lot of pain in the Jetbrains community, it's horror to have to reboot Windows a couple of time each day when the WSL freeze happens. |
@schiorean the issue has been fixed some months ago in WSL v0.58.0. |
Looks like it's not fixed, I'm running 0.66.2. Or it's another related bug, but the symptom is the same: WSL (and WSL commands) freezes and the only way to make it work again is to restart the computer. |
It's another bug and probably not even related to this one. The symptoms are not the same: WSL itself never froze due to this bug, the distro itself was running just fine, only the interoperability with Windows was lost. This bug has been fixed. I haven't had it occur once since 0.58.0. |
Same here running 0.66.2.0 and have to reboot mostly after my Suface Book was in standby. @schiorean have you found or created an issue for that? |
@cubic3d no I didn't find or add a new issue. I added an issue on the Jetbrains issue tracker though. |
@sufius now that it's been a couple of weeks - was that the root cause for you? Did excluding from windows defender make the difference? |
@nrclark Yes, my problem was solved by this exclusion. |
Version
WSL 0.50.2.0
WSL Version
Kernel Version
5.10.74.3
Distro Version
Ubuntu 20.04.3 LTS
Other Software
No response
Repro Steps
I'm not sure what went wrong nor how to debug this. It was working fine before but all of a sudden I stopped being able to use windows commands from inside WSL.
notepad.exe
,wsl.exe
, etc they all just hang forever and not even Ctrl+C is able to kill them and I'm forced to close the terminal.Expected Behavior
Can use windows commands from inside WSL (e.g.
wsl.exe --version
)Actual Behavior
Windows commands (e.g.
wsl.exe --version
) hang forever and not even Ctrl+C is able to kill them and I'm forced to close the terminal.Diagnostic Logs
nodepad.exe
wsl.exe --version
The text was updated successfully, but these errors were encountered: