YCM does not exit when vim exits

[gh67uyyghj]

I am using vim 8 on Archlinux and YCM is installed using Vundle. The problem is I found that there are many python processes left running as many as the vim instances I opened and then closed. i.e. YCM doesn't gracefully exit when I quit a vim instance. I don't know if this is a bug but I really doubt this belongs to any vimrc option. I am ready to show any further details but I frankly I don't know what to show currently. I need some help in this. Thanks!

[micbou]

Start Vim with YCM enabled and type the following command:

:py3 ycm_state.OnVimLeave()

Does it result in an error? Is the Python process still up after this command?

[l3nkz]

I have the same problem. ycmd continues executing after vim is closed and consumes an significant amount of memory this way.

If I execute you given command, I get the following error:

Traceback (most recent call last):
   File "<string>", line 1, in <module>
NameError: name 'ycm_state' is not defined

If i execute the command with the python2 interpreter, it does not give any error message or other output but kills the ycmd server associated with this file.

[micbou]

@l3nkz Which OS and Vim version? Is the ycmd process not terminated each time you are closing Vim or does it happen randomly?

[l3nkz]

@micbou I use an up-to-date Arch Linux with vim 8.0 with patches 1-55. I installed YCM via vundle and update it regularly. The ycmd process is never terminated together with vim. I can reproduce it very easily.

[vheon]

The ycmd process is never terminated together with vim. I can reproduce it very easily.

But does it terminate right after or it doesn't terminate at all?

[l3nkz]

The ycmd process is not terminated at all. I have to manually terminate it by sending SIGTERM to it. To be fair, I haven't checked if it terminates after some hours, because I am working in a VM with to little memory ;)

[micbou]

It looks like YCM VimLeave event is not triggered when you are closing Vim. What's the output of :au VimLeave?

[l3nkz]

This command gives the following output for me.

:au VimLeave
--- Auto-Commands ---
youcompleteme  VimLeave
    *         call s:OnVimLeave()

[micbou]

So, YCM VimLeave autocommand is properly registered. Could you run the following command:

vim -c "autocmd VimLeave * call writefile([v:dying], 'vim_leave', 'a')" -c ":q"

in a terminal? This should create the vim_leave file in the current directory with 0 as its contents. If the file doesn't exist then it's not an issue with YCM but with Vim not triggering the VimLeave event when exiting.

[l3nkz]

This command properly creates the vim_leave file.

[micbou]

And what about the ycmd process?

[micbou]

I really can't reproduce the issue on my ArchLinux VM with Vim 8.0.55. This could be a bad interaction with another plugin. Is the ycmd process still up after closing Vim when starting it with this minimal vimrc?

set nocompatible

set rtp+=~/.vim/bundle/YouComplete

filetype plugin indent on

syntax on

[l3nkz]

Using this minimal vimrc fixed the problem for me. Thank you very much. I will dig deeper and see if I can find the plugin causing the behavior. Sorry for the noise.

[vheon]

So closing for now 😉

[erahhal]

I had the same problem, and did disabled my plugins one at a time, and found that the jistr/vim-nerdtree-tabs plugin was causing the problem. It may be NeoVim specific. See:

vim-nerdtree-tabs issue 76