Blue

Well the VM freezing would cause timeouts and closed sockets from the Windows' perspective, which would cause those errors (especially if the OOM triggers). Closing since enabling swap solved the...

@jmaoito: WSL doesn't directly control the Linux paths, those are controlled by `/etc/login.defs`, `/etc/environment`, your shell profiles and `WSLENV`. This is most likely caused by something in either of those....

What @zcobol and and @elsaco said is right. We indeed added logic to capture coredumps in 2.3.17. The default path is `%tmp%\wsl-crashes`. You can override the crash dump folder via:...

@paul-haskell: You most likely have an older build installed. Try running: wsl --update --pre-release to get the latest.

@paul-haskell: Can you collect /logs of this happening (for both scenarios) ?

Thank you @paul-haskell. Looking at the logs, I see that a crash dump is generated: ``` Microsoft.Windows.Lxss.Manager LinuxCrash 09-20-2024 14:40:57.101 " " "FullPath: C:\Users\phaskell\AppData\Local\temp\wsl-crashes\wsl-crash-1726868457-485-_mnt_c_phaskell_CS221_Private_ClassDays_Day17_makeCore-6.dmp Pid: 485 Signal: 6 process: !mnt!c!phaskell!CS221!Private!ClassDays!Day17!makeCore...

@paul-haskell: Does disabling systemd and restarting the distro help with case 2?

Can you by setting ``` [boot] systemd=false ``` in /etc/wsl.conf

Thank you @paul-haskell. I wonder if this could be namespace issue. What if you try to write the dumps to `/mnt/wsl` instead ?

Ok that's good to know. The short version is that WSL creates different mount namespaces for distributions (and even within distributions in some usecases). `/mnt/wsl` is a mountpoint that all...