Page Comparison

...

If you want to end your remote session, click the green "SSH connection status" box in the lower left corner. In Then, in the input box that opens, select the "Close Remote Connection" option. If you simply close your VS Code window, some server-side components of VS Code will continue to run remotely.

...

Kill the leftover orphan processes in the login nodes

...

VS Code is a handy tool, but comes with some side-effects that may affect you and other users of Setonix. One of these problematic side-effects is the unexpected left over of orphan processes consuming resources in the login nodes even when users have ended their VS Sessions or turned-off their computer. If Visual Studio Code has left some related processes running on the login nodes, these may use CPU and complicate you and other users to log into Setonix. The current solution for this is a bit painful and requires the use of manual investigation/cleaning by users.

...

$ ps -fea | grep ${USER} | grep -i "vscode" | grep -v "grep" | awk '{print $2}' | xargs kill -9

#Confirm that no vscode process exist:
$ ps -fea | grep ${USER} | grep -i "vscode" | grep -v "grep"
$

...

If you find that after killing orphan processes in all the login nodes is still giving you problems to login using VS code. Then, you may need to purge the Visual Studio Code directory on Setonix using the following:

...