gistfile1.txt

Seems more likely now.

First, what version of WSL are you on? 

> wsl.exe --version

Second, to confirm this, we would add:

[wsl2]
debugConsole=true

to $env:USERPROFILE\.wslconfig

Then > wsl.exe --shutdown

Open WSL, a kernel debug output console will open, you can minimize.

Wait for it to happen again, then go check the debug output.

I tried to overstress WSL memory usage with stress-ng to get you an example of what the memory compaction debug output looks like, but despite using 16GB+ and running out of memory to the point the kernel was killing processes, I couldn't get it, but WSL was cleanly switching from ~2GB to 16GB of RAM and back. Which leads me back to what version of WSL you might be running.

If you can't upgrade your WSL version for some reason, alternatively, you could just set a max RAM and disable this feature in .wslconfig and see if these hangs end:

[wsl2]
memory=4GB
pageReporting=false