High GPU Usage if WSL is Disconnected

• VSCode Version: 1.57.1 507ce72a4466fbb27b715c3722558bb15afa9f48 x64
• Local OS Version:

Edition		Windows 10 Home
Version		21H1
Installed on	‎5/‎17/‎2021
OS build	19043.1052
Experience	Windows Feature Experience Pack 120.2212.2020.0

• Remote OS Version: Ubuntu 20.04 on WSL 2.0
• Remote Extension/Connection Type: SSH/Docker/WSL
• Logs:
  Probably not super useful since restarting WSL appears to have wiped them. Here's what I have after restarting WSL

[2021-07-06 03:09:51.313] Resolving wsl+ubuntu-20.04, resolveAttempt: 1
[2021-07-06 03:10:00.322] Starting VS Code Server inside WSL (Ubuntu-20.04)
[2021-07-06 03:10:00.322] Extension version: 0.56.5, Windows build: 19043. Multi distro support: available. WSL path support: enabled
[2021-07-06 03:10:00.322] No shell environment set or found for current distro.
[2021-07-06 03:10:00.474] Probing if server is already installed: C:\Windows\System32\wsl.exe -d Ubuntu-20.04 -e sh -c "[ -d ~/.vscode-server/bin/507ce72a4466fbb27b715c3722558bb15afa9f48 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2021-07-06 03:10:00.629] Probing result: found
[2021-07-06 03:10:00.630] Server install found in WSL
[2021-07-06 03:10:00.630] Launching C:\Windows\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 507ce72a4466fbb27b715c3722558bb15afa9f48 stable .vscode-server 0  '}
[2021-07-06 03:10:00.782] Setting up server environment: Looking for /home/dirthsj/.vscode-server/server-env-setup. Not found.
[2021-07-06 03:10:00.782] WSL version: 5.4.72-microsoft-standard-WSL2 Ubuntu-20.04
[2021-07-06 03:10:00.782] WSL2-shell-PID: 13
[2021-07-06 03:10:00.782] Starting server: /home/dirthsj/.vscode-server/bin/507ce72a4466fbb27b715c3722558bb15afa9f48/server.sh  --port=0 --use-host-proxy --without-browser-env-var --print-ip-address --enable-remote-auto-shutdown  
[2021-07-06 03:10:00.782] 
[2021-07-06 03:10:00.782] 
[2021-07-06 03:10:00.782] *
[2021-07-06 03:10:00.782] * Visual Studio Code Server
[2021-07-06 03:10:00.782] *
[2021-07-06 03:10:00.782] * Reminder: You may only use this software with Visual Studio family products,
[2021-07-06 03:10:00.782] * as described in the license https://aka.ms/vscode-remote/license
[2021-07-06 03:10:00.782] *
[2021-07-06 03:10:00.782] 
[2021-07-06 03:10:00.782] IP Address: 172.20.112.44
[2021-07-06 03:10:00.782] Extension host agent listening on 36589
[2021-07-06 03:10:00.782] 
[2021-07-06 03:10:00.785] Pinging 172.20.112.44:36589...
[2021-07-06 03:10:00.857] 172.20.112.44:36589 responded
[2021-07-06 03:10:00.857] WSL resolver response: 172.20.112.44:36589
[2021-07-06 03:10:00.857] To debug connection issues, open a local browser on http://172.20.112.44:36589/version

Steps to Reproduce:

1. Build the boost c++ library within the integrated terminal running from WSL 2.0, using the WSL 2.0 filesystem
2. WSL will sometimes (~15% of times) stop responding and a message will pop up saying disconnected.
   Note: I have managed to trigger this in other ways, such as moving a large quantity of files, but this is the easiest to reproduce
3. During this time, observe task manager. GPU usage spikes up to 30% -- on an NVIDIA GeForce RTX 3060 Ti. Normal usage is less than 1%,
   

Does this issue occur when you try this locally?: Yes/No
Does this issue occur when you try this locally and all extensions are disabled?: Yes/No

Start by reproducing the boost C++ build in the integrated terminal on the WSL 2 filesystem and observe Task Manager during the disconnect. Review the reported WSL resolver and server logs; done means identifying and addressing the GPU spike that occurs when WSL stops responding.