Open blueyed opened 6 years ago
If the deoplete main process exits with an error it will stay around as a Zombie process.
How can it exit yet "stay around"? Which process exactly?
@justinmk
AFAIK a process becomes a zombie process for a parent's wait
.
So it looked to me like Neovim's loop handling might never trigger that wait
for some reason, but I have not investigated further, and unfortunately could not reproduce it using a simpler script back then.
I've noticed that if the deoplete main process exits with an error it will stay around as a Zombie process.
I couldn't reproduce it with a standalone script outside of Neovim, so I assume there might be something in Neovim's python-client that might cause it.
Deoplete's source: https://github.com/Shougo/deoplete.nvim/blob/a80fd5267e978ab86a1e30975be9457df3394646/rplugin/python3/deoplete/parent.py#L92-L98
Test script:
Needs further investigation (also from my side), but maybe you have some pointer(s) already?
/cc @shougo