neovide: Random freezes with toggleterm

Describe the bug Neovide randomly freezes, when toggleterm is open. The only way to close it is to terminate it or the nvim process.

The task manager shows neovide using 60-100% of the CPU core, zsh from toggleterm using 100% (either no program running inside or one that isn’t currently interacting with the shell), and nvim process also around 100% and also continuously eating more and more RAM. (see the attached screenshot)

To Reproduce This is the worst about it, it happens quite randomly. The only common denominators in all the cases it happened were:

• neovide (no issue in plain nvim)
• using it for an hour or more
• toggleterm open in floating mode with more than one screen of output
• either keypress or mouseclick anywhere in the neovide window, after having another program in focus, but could have been already frozen before that, hard to tell

And it’s like once in day (multiple hours of use) and on one PC and not on another one with the same lua config (but not the same versions of stuff).

Expected behavior No freezes 😃

Screenshots

Desktop:

• Neovide 0.11.2
• OS: 6.6.4-2-MANJARO x86_64 GNU/Linux

Please run neovide --log and paste the contents of the .log file created in the current directory here: neovide-backtrace.log that appears in the directory after the neovide process (or the nvim inside) is terminated

2023-12-04 18:48:57 - Neovide panicked with the message 'Mouse Input Failed: DecodeError(ReaderError(Custom { kind: UnexpectedEof, error: "EOF" }), "nvim_input_mouse")'. (File: src/bridge/ui_commands.rs; Line: 71, Column: 18)
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>

I am not sure, but the timestamp feels like it was some time before the freeze (the shell shows I opened the btop to kill it at 19:03), but I hadn’t noticed any other issue before it happened and it is quite consistent among all the freezes, so it’s probably related.

Yeah, I know it’s not a lot of info and I’d be happy to provide more or help in any other way with debugging. (I will try running it always with --log from now on to catch the next freeze). I really enjoy neovide but this is kinda annoying.