I was considering making a GH issue, but I don’t think I have enough information for it to be useful, so I thought I’d ask here first.
I’ve been happily using neovim as one of my primary editors for years across my Mac and a few Linux (Arch, Raspbian, NixOS) systems; since 0.6 it’s more and more becoming my primary! I am usually running it inside tmux.
However, I’ve had an intermittent freezing issue for years that I’d love to learn how to debug.
Essentially, the neovim window just seems to almost freeze – no keys seem to register. I can still switch tmux panes back and forth to and from neovim and it seems to work (the cursor activates), but nothing else registers –
:qa!, etc etc – like nothing is being pressed. Happens on both Mac and Linux. From another pane,
pkill nvim does nothing; I have to
pkill -9 nvim which immediately works.
Today, when I finally decided to dig in a bit, I tried looking under
strace and I don’t see any other output other than this one line:
$ sudo strace -p $(pgrep nvim) strace: Process 868731 attached futex(0x55bc5752276c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY
gdb and attached to the process, but frankly I don’t know what to do from there.
When this hang happens again (I wish I knew how to reliably trigger it – it just seems random), what can I do to debug or gather more information on what is going on?
I presume it could be an issue with a plugin, but it only happens once every couple of days, so I imagine selectively disabling plugins could take a long time to determine whether or not the issue is associated with a specific plugin. Is there another approach I could try?
Thanks in advance for any suggestions.
EDIT: Also should note that I don’t see this behavior with any other app I can think of, including vim.