We set a 1min timeout for extensionHost processes that are no longer seeing a client connection to be killed. These (more specifically their Lean server children) are the most memory-hungry processes, so this mostly suffices. However, the extensionHost's vscode-server parent should also be killed eventually, and yet it sticks around for a long time (or even indefinitely? not sure). We should reduce the timeout.
We set a 1min timeout for extensionHost processes that are no longer seeing a client connection to be killed. These (more specifically their Lean server children) are the most memory-hungry processes, so this mostly suffices. However, the extensionHost's vscode-server parent should also be killed eventually, and yet it sticks around for a long time (or even indefinitely? not sure). We should reduce the timeout.