Flood of connection errors and many processes spawned

Sometime in the last two weeks I started getting the error Connection to server is erroring. Shutting down server. in VSCode’s output window with varying frequency during coding sessions. Today while during a lag spike I took a look at the task manager and saw about 20 R terminal front-end processes each taking nearly 100mb of ram. When I killed each process I got an error in VSCode like this one:

[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
[Error - 7:41:10 pm] Connection to server is erroring. Shutting down server.
R Language Server (18440) exited with exit code 1

I’m on Windows 10, using the latest versions of VSCode and the LSP extension, R 4.0.2, and languageserver 0.3.6

[D3SL]

After giving this a bit of use it looks like this is resolved for me too. A reasonable number of processes are spawned up front and they actually close on their own now. Being able to use VSCode instead of RStudio is a big quality of life improvement, to say nothing of the competition to the RStudio monopoly being vital for the R ecosystem’s health.

[D3SL]

As noted in this comment I’ve tried that without success unfortunately.

Hi, Maybe you can try to set environment variable R_LANGSVR_POOL_SIZE in your ~/.Renviron to limit the languageserver process, as indicated by renkun-ken.

~/.Renviron in Windows should mean C:\\Users\\user\\Documents\\.Renviron. You could try file.edit("~/.Renviron") in R. If R_LANGSVR_POOL_SIZE=0 is properly specified, then a vscode instance with a R workspace folder open will only spawn two R processes that are constantly running in background, one for languageserver, and the other for R help server. The languageserver will spawn at most two more child processes as you open or change a document but will terminate once the task is done.