I am running into serious issues with nim 1.6.0 when using VS Code. VSCode seems to be creating a lot of nimsuggest processes which never end, resulting on my windows PC running out of memory and crashing after a while.
Checking with process explorer I can see that on the process tree the code.exe process creates manu nimsuggest.exe processes, each of which creates a conhost.exe process and another single nimsuggest.exe process. This is not recursive (i.e. it is not code creating 1 nimsuggest.exe process which creates another one, etc). The code.exe process creates _many nimsuggest.exe processes, and each of them creates a single conhost.exe and a single nimsuggest.exe process (which does not creates other processes below it).
This makes it impossible to do any coding using VS Code. The problem does not happen if I switch back to nim 1.4.8 (which only creates a couple of nimsuggest processes with their own conhost and nimsuggest children) so this seems to be a regression in 1.6.0.
I'm using the nim-based VS Code extension. Does anybody else have this problem?
I noticed this yesterday when trying to use the vscode extension written in Nim. It opened a bunch of nimsuggest.exe processes. With the typescript extension this problem does not occur.
I believe there may be some problem in the extension. I didn't have a lot of time to check it out.
it's an old issue
basically the extension doesn't know which file is the root/main of your project, so it has to open a nimsuggest file for each .nim file you open/edit. Question is why those processes not always die automatically when files are closed.
You can do 2 thigs:
there are existing issues opened on this on github