1265453673

> Also can you upgrade to 2.5.9 by running `wsl --update --pre-release` and check if the issue still exists with that version ? Not using docker. I've already got the...

I've increased the memory head room which delays the crash, which leads me to think that WSL doesn't handle reaching this limit well in the newer version. .wslconfig ``` [wsl2]...

@OneBlue this issue still persists, do you need further information?

@OneBlue I've submitted the logs, after upgrading to version 2.6. It appears when the memory runs out on the machine, I still get the following error message: Catastrophic failure Error...

> Thank you [@1265453673](https://github.com/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...

> Thank you [@1265453673](https://github.com/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...

> [@1265453673](https://github.com/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 > ``` Thanks that did...

Actually it does still respond to the debug shell after the crash, here's its output. [OutputAfterCrash.txt](https://github.com/user-attachments/files/21504699/OutputAfterCrash.txt)

Thanks for taking a look at the logs. Sounds like it is in fact an application issue.