3 ms·
Watch out for VRAM/RAM. When programs on WSL tired to take more than there was available it was crashing my WSL hard and even corrupting files on the virtual dr
by scotty79 4mo ago
Watch out for VRAM/RAM. When programs on WSL tired to take more than there was available it was crashing my WSL hard and even corrupting files on the virtual drive attached to WSL in a very strange manner that made recent files just disappear. I had at leat two projects that had to be rebuilt from past conversation with AI because all their files were gone after few crashes.
I asked codex to write WSL config to prevent crashes. It put some limits on WSL and the situation stabilized, but I lost all trust for WSL anyways.
- fallinditch 4mo agoWhat are the config settings you needed? TIA
- scotty79 4mo agoThat's my wslconfig file located in my %USERPROFILE% dir: [wsl2] memory=40GB processors=8 swap=8GB swapFile=C:\\wsl-swap.vhdx localhostForwarding=true guiApplications=false vmIdleTimeout=30000 maxCrashDumpCount=3 [experimental] autoMemoryReclaim=gradual I have 64GB of RAM and 24GB of VRAM.