New Node Process for every Nvim Instance Eating up alot of RAM

[JadAbouHawili]

Everytime I open a new neovim instance(i.e typing nvim in the terminal , whether or not your opening a file/buffer doesn't matter) the following process pops up:

node ~/.npm/_npx/8784704caaadcd38/node_modules/.bin/copilot-language-server --stdio

For example, opening two terminals and typing 'nvim' causes two process like this to appear. When closing nvim , these processes linger on taking up RAM until they eventually die(don't know how much time , but not being killed immediately is too long)

A similar issue is currently open in the pure lua replacement of this plugin copilot.lua

I have disabled this plugin because using it is unbearable on a system with limited RAM

[dherrera1911]

I am running into the same problem. I work with multiple vim sessions across tmux splits. Each starts a copilot-language-server using ~1GB of RAM.

A solution that worked for me was moving copilot.vim into ~/.vim/pack/github/opt/copilot.vim, so that it is not automatically initialized with vim. Then, I added the following to my .vimrc:

" Define a command to start Copilot on demand
command! Copen packadd copilot.vim | sleep 200m | execute "Copilot enable" | execute "Copilot status"

Now when I want Copilot active I call :Copen, which loads the package, enables copilot, and starts the language server.

The command looks clunky because things failed with simpler commands.

[ToHe-MT]

I also happen to have this same problem. Multiple copilot-language-servers. each taking 1GB or RAMs