This also happen when on battery without doing anything WSL2 releated (but with Docker Desktop running), killing autonomy. Vmmem "randomly" uses high cpu/power amount (60%-70%) for couple of minutes (2 to 5 min) before settling down. WSL2 stay idle when no user workload are launched. My machine (Lenovo X1 Carbon) has 16GB of RAM and usually Vmmem RAM consumption float around ~4GB.Įxcluded those hiccups WSL2 experience is pretty neat and flowlessy. In the past I tried to alleviate the issue with a. Docker Desktop (Windows) v3.3.3 (64133) running (with mongo or postgres). ![]() ![]() VSCode Insiders v1.57.0 with WSL Remote v0.56.2 for personal projects (usually JS related).VSCode Stable v1.56.2 with WSL Remote v0.56.2 for work (usually Java + SQL).not running Docker Desktop and WSL2 "only"), but I failed miserably. I tried to isolate the failing component (ex. Whit this issue I'd like to gather feedback on how to collect the most useful information to debug this behavior. But looks like more prominent when waking up from sleep. I'm struggling to actually repro this issue deterministically.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |