Closed janbernloehr closed 4 years ago
I've compiled Chromium before in WSL, so I cannot replicate this exact issue at the moment. This might be your computer at fault here.
Download a large file, pull a large git repo, run a long build
That cannot be turned into an actionable.
I was not able to reproduce this on a second machine. Seems to be the the install is broken.
I have the same issue. I tried on a second machine and the same issue. On both AMD and Intel systems happens. I tried to pull a big repo and after like 25-35 minutes I get the same error mentioned in OP. Running latest version of Windows 10 Pro...
I have the same issue. It happens under heavy load like the OP. I reinstalled distros and it always happens. One big git clone and some long apt-get π₯
I've been experiencing the same issue for a while and I seem to be able to reproduce it every time the host free memory is depleted (last segment in Task manager, standby memory is not reclaimed). Htop on guest seems to see more memory than the amount of free memory actually available, and even greater than the sum of free + standby. May this be the cause? [WSL2, Ubuntu, running many heavy JVM processes]
same issue, happened for me when downloading a huggingface 10GB model
There has been some evidence of WSL2 misbehaving under memory pressure. It is also probably the underlying cause of #4899. If anyone is experiencing (air quote) "badness under some period while doing big things", like and subscribe #5410, which has the benefit of a repro and being open. I had some luck with artificially decreasing my physical RAM and a ginormous Windows page file. YRMV.
Environment
Steps to reproduce
Expected behavior
Actual behavior
[process exited with code 1]
.This may be related to #4899 but is different in the sense that the issue shows up after some time only.
Things we tried