Blue
Blue
Thank you for reporting this @1265453673. Are you using docker by any chance ?
Also can you upgrade to 2.5.9 by running `wsl --update --pre-release` and check if the issue still exists with that version ?
@1265453673: If you're not using docker, let's try to collect a full repro repro under log collection so we can understand what's going on. Can you please: - Update WSL...
Thank you @1265453673. Looking through the logs, I can see that the error is caused by a timeout when trying to create a new process. Let's try something. Can you...
Thank you @1265453673. That's unfortunately expected. Only one debug shell can be connected per VM. Could you share when the shell froze, and what the output was so far ?
@1265453673: Unfortunately, not easily. One thing you could do is (powershell): ``` curl.exe https://raw.githubusercontent.com/microsoft/WSL/refs/heads/master/diagnostics/dump-init.sh | wsl --debug-shell | Tee-Object -FilePath Output.txt ```
Thank you @1265453673. Looking at the log I can se that the VM is running out of memory, which is most likely why it gets into a "broken" state. You...
Thank you @carlosedp. Interestingly I don't see any loglines regarding that mount failing. Could you: - Remove the "LABEL=cloudimg-rootfs / ext4 defaults 0 0" line from the fstab ? It...
Thank you @fzh075. Can you capture /dumps of WSL processes when it gets into that "stuck" state ?