smjonas
commented
3 years ago Possibly related: I also had these Neovim crashes lately which I never had before. For me they sometimes happen when resizing the Neovim application window. Since I have not updated Neovim since 0.5 stable, this very likely has to do with some plugin, although I am not sure which one yet. I will try to reproduce the crash more reliably. @gkapfham is there a way I can see the exact Neovim error like segmentation fault etc.? Is there some file that logs these errors?
gkapfham
ms-jpq
akaswenwilk
Hello! Thanks for creating the coq_nvim plugin! I have really appreciated how easy it is to get it up and running and the speed with which is suggests the completions. It is also impressive how it works so well with the LSPs that I have setup for different languages! In summary, I'm really thankful for this plugin and I hope that you continue to improve it!
When I started using this plugin I initially found it to be very stable. However, recently I find that when I accept at least one completion accepted by coq_nvim when I am editing a commit message in Neovim using Fugitive then Neovim crashes with a
segmentation fault (core dumped)message. What I have found is that Neovim never crashes in the same situation if I do not accept one of the completions suggested by coq_nvim. However, as soon as I accept at least one completion there is at least a 30% chance that I receive one of the following messages after Neovim crashes:double free or corruption (out)abort (core dumped) nvimsegmentation fault (core dumped)After extensive experimentation I regret that I cannot better explain the failure condition than what I have provided in the previous paragraph. To be clear, I have not yet invested enough time to absolutely localize the problem to the coq_nvim plugin — it could be something else in my configuration and I've not yet done enough delta debugging to confirm that it is definitely related to the acceptance of a completion suggested by coq_nvim. With that said, I thought it might be helpful if I raised the issue now so that we could at least briefly discuss this potential problem and then decide on a way forward. I have also searched this project's issue tracker and I did not see any reports of this problem.
Here are some additional details about the configuration on my computer:
Operating System:
Linux 5.13.13-arch1-1 #1 SMP PREEMPT Thu, 26 Aug 2021 19:14:36 +0000 x86_64 GNU/LinuxNeovim Version:
Git Version:
I am also running Neovim inside of a
tmuxsession. Here are the details abouttmux:Python Version:
It is also worth noting that I install and use Python through
pyenv. I'm not sure which version of Python your plugin picks up automatically, by this is the one that I am currently using:I configure Python inside of Neovim with the following source code:
I am currently running
tmuxand Neovim inside ofzsh. Here is the configuration:Here is my minimal configuration of this plugin:
I am currently using vim-plug to install the plugin with:
I have tried several different configurations of coq_nvim and I can't find one that avoids the segmentation fault. With that said, it is worth noting that coq_nvim never causes a segmentation fault unless I am editing a commit message. That is, the plugin always works flawlessly when I edit course code and accept completions in any type of buffer except for a Fugitive or Neogit buffer that enables me to edit the commit message. I can also confirm that I always run the
COQdepscommand whenever the coq_nvim plugin requests that I do so. To date, I've never seen that process crash or repot any errors after the dependency update process.Here is an example of a screen shot where I am editing
file.txtby placing "lorem ipsum" text inside of it and then using Fugitive to write a commit message. After coq_nvim suggests some completions I pick them, normally using words like "consetetur" and "eirmod" and "nonumy". After I attempt to save the commit message with Fugitive I receive the segmentation fault error. I can confirm that this happens with files written in JavaScript, Python, Markdown, and Vim configuration. It seems unlikely that the problem is specifically connected to Fugitive because the same segmentation faults occur with I edit a commit message with Neogit. Finally, I don't have any evidence that the problem is with Neovim itself because if I disable coq_nvim or I don't accept its suggested completions then I never have a segmentation fault and a crash of Neovim.Thanks for taking the time to read this issue! Is there any other information that you would like me to provide so that I can best support the debugging of this problem? I would be glad to help as best as I can so that we can work together to determine if the problem is, in fact, related to coq_nvim and the accepting of completions inside of the Fugitive or Neogit buffers.
In summary, it would be awesome if you could point me in the right direction to further debugging this issue. If you think that this might be a problem in coq_nvim, it would be great if you could resolve it in a forthcoming version of coq_nvim. If you don't think that the problem is in coq_nvim then any ideas that you can share would also be very greatly appreciated! Thanks!