If you use Windows Subsystem for Linux, you should soon find that it's much more stable and less likely to crash your host system.
Windows Subsystem for Linux has just received a major structural redesign for how it handles system resources so that catastrophic failures under heavy loads are less likely. This update introduces memory and CPU caps so that the underlying Windows host processes don’t run out of resources themselves.
Before this patch was applied, it was possible for users to run resource-heavy processes, like compiling software, that caused the virtual Linux environment to regularly trigger Out-of-Memory (OOM) events that didn't just crash active applications, but used up all the resources that the core WSL engine itself needed to run. This would leave WSL entirely unresponsive, even after the memory spike subsided.
The fix that Microsoft has just accepted imposes a hard resource limit on the virtual Linux environment via a sandbox. This ensures there is always enough memory and CPU power to keep the WSL host processes alive. So now, if you attempt to compile a program in the Linux environment and it runs out of resources, that process will crash, but not the overall WSL.
To achieve this, the fix ensures the system places all user-run environments into a restricted control group called wsl-user. This group is capped at exactly 32MiB less than the host’s total RAM and 0.01 cores below the total CPU capacity. This thin margin should be enough for WSL to keep vital background communication and system orchestration alive.
Another important detail worth mentioning is that WSL has had to transition fully to Linux cgroup (control group) v2. Unfortunately, this breaks backward compatibility with legacy workloads if they rely on the older framework. If you really need cgroup v1, then you need to add IsolateDistroCgroup = false to your .wslconfig file, which bypasses the new measures.
Finally, this change comes with another benefit. If you run multiple Linux environments side-by-side, you will no longer run into initialization blocks. The new architecture isolates systemd instances into per-distro cgroups so that they boot independently.
Source: WSL GitHub
Hope you enjoyed this news post. Feedback welcome.
Posted Tuesday 14 July 2026 at 5:41 pm AEST (my time).
News posts: 2023 5,800+ | 2024 5,700+ | 2025 5,700+ | 2026 (to end of June) 2,475
- Tzcon
-
1
Recommended Comments
There are no comments to display.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.