Anyone having issues with the Store version of WSL ?

[AbdealiLoKo]

Hey, I had an issue when I recently switched my user account.

The main culprits I could see are:

1. ADS user has issues 🔴 ... Local user does not 🟢
2. WSL via Store has issues 🔴 ... WSL with wsl --install does not 🟢
3. Ubuntu 22.0 has issues 🔴 ... Ubuntu 20.04 does not 🟢

I'm wondering if anyone else has seen similar issues to what I have seen

Longer story of what I am seeing:

So, I was earlier using user1 on my Windows 10 (all the latest updates have been installed)
And I moved to user2 which is ADS controlled

In user1 I had installed WSL with wsl --install - and have not faced any major issues.
About a year ago I faced issues with WSL taking over all my CPU and RAM - but then:

1. Setting limits in .wslconfig
2. and adding a pagefile in my windows (and gi ing some swap space to Ubuntu)
   solved the issue and things were smooth sailing.
   I was using Ubuntu 20.04

Now that I was moving to user2 - I tried installing WSL from Windows Store (cause I don't have admin privilege anymore)
And I used Ubuntu 22.04 with that Store-WSL.
I have copied the same .wslconfig

In the new account - I have been seeing some very weird issues:

1. My laptop heats up at times
2. My WSL randomly just hangs up - and doesn't react to any keystroke.
3. When it hangs - opening a new terminal just shows me a blank screen

If I am actively using WSL (normally vscode or jupyter or angular is running) it happens 2-3 times a day
When I don't actively use WSL it happens once a day

My debugging:

• When I open Task Manager - it shows me "System Interrupts" is taking up a lot of CPU
• I even tried keeping htop open all the time in my WSL to keep track - and I could see that all my 4 CPUs in htop show up as 100% even though I am not doing anything major !
• It seemed like vscode processes were using up most of the CPU (sometimes with ms-python and sometimes typescript extensions)
• I even tried to disable all my extensions in vscode but it didn't help much.
• But I don't think it is a vscode issue - cause there were cases where I just started jupyter notebook server and the WSL got "stuck"
• And all my vscode extensions + jupyter things were stuff I was doing earlier too without any trouble