-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deoplete-go freezes forever sometimes #98
Comments
@clee Thanks issue and sorry for late reply. |
Not reliably; it seems to happen more when/if I leave neovim running for a long time (like, 24+ hours). Having any open neovim sessions with Go files, once the freezing starts, makes it impossible to enter insert mode in any of them. Exiting all neovim processes and re-launching neovim makes things work again for a while. |
@clee Thanks reply. got it. |
Not sure we have the same problem but re-installing gocode seemed to fix my deoplete freezing forever issue. I ran |
@clee Please try |
@clee Still reproduce-able? |
Still happens occasionally. Seems to be more frequent when I put an instance of neovim with a Go file open into the background (with Ctrl+Z). |
@clee Please try |
@Shougo I run I'll see if I can figure out how to reproduce this reliably and report back with steps if I can. Update: Following these steps, it happened on the first try, but not again after trying it three more times.
After step 3, for me, the nvim process with the second file open was locked completely, and I could not move the cursor or enter insert mode. Opening more nvim processes on further go files resulted in all of the new processes being locked. But this does seem to be pretty difficult to reproduce reliably. I'll keep testing to see if I can figure out any other conditions that might make it more likely. |
It may be neovim or neovim-python problem(or feature). We cannot fix the problem. |
I also frequently have this problem. Pressing ctrl-C a couple of times unfreezes it, but disables deplete. This is the stack trace that is printed from calling
|
@romeovs Please read this. It is not deoplete and deoplete-go problem. |
Using gocode revision
843b7a63f621bb441274849d58671870adf1a5ce
and deoplete-go revision7990da5c8c89a47e0ccd3b7e60a836a6f115641a
, when I edit JSON metadata, neovim completely locks up attempting to get autocomplete from gocode through deoplete-go.I can reproduce this on multiple machines by inserting the cursor after the
e
injson:"name"
inside https://github.com/clee/channon/blob/master/types.goThe text was updated successfully, but these errors were encountered: