neovide: Exiting neovide on windows leaves orphaned neovim processes around

Describe the bug Closing neovide by any normal means results in 2 neovim processes being left running indefinitely. After a few days I have had upwards of 10 that are taking up a sizeable amount of memory for nothing.

To Reproduce Steps to reproduce the behavior:

Start neovide
Close it
Look at task manager, 2 neovim processes are still running

Expected behavior Close down the neovim processes during teardown.

Screenshots If applicable, add screenshots to help explain your problem. After closing neovide with :q

Desktop (please complete the following information):

OS: Windows 11 22635.3140
Neovide Version: 0.12.2
Neovim Version: 0.10.0-dev-2465+ga7788c2e2 , latest nightly on scoop at this time

Please run neovide --log and paste the contents of the .log file created in the current directory here:

Log from receiving Q KeyEvent

TRACE [neovide::window::keyboard_manager] KeyEvent {
    physical_key: Code(
        KeyQ,
    ),
    logical_key: Character(
        "q",
    ),
    text: Some(
        "q",
    ),
    location: Standard,
    state: Pressed,
    repeat: false,
    platform_specific: KeyEventExtra {
        text_with_all_modifers: Some(
            "q",
        ),
        key_without_modifiers: Character(
            "q",
        ),
    },
}
TRACE [neovide::window::keyboard_manager] Key pressed q ModifiersState(0x0)
TRACE [neovide::channel_utils] UICommand Serial(Keyboard("q"))
TRACE [neovide::bridge::ui_commands] In Serial Command
TRACE [neovide::bridge::ui_commands] Keyboard Input Sent: q
TRACE [neovide::bridge::handler] Neovim request: "neovide.quit"
INFO [neovide::running_tracker] Quit with code 0: Quit from neovim
DEBUG [neovide::settings::window_size] Saved Window Settings: {"window":{"Windowed":{"position":{"x":370,"y":201},"pixel_size":{"width":1838,"height":1025},"grid_size":{"width":183,"height":51}}}}
DEBUG [neovide::settings::window_size] Saved Window Settings: {"window":{"Windowed":{"position":{"x":370,"y":201},"pixel_size":{"width":1838,"height":1025},"grid_size":{"width":183,"height":51}}}}
DEBUG [neovide::settings::window_size] Saved Window Settings: {"window":{"Windowed":{"position":{"x":370,"y":201},"pixel_size":{"width":1838,"height":1025},"grid_size":{"width":183,"height":51}}}}
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::channel_utils] neovim_handler MouseOff
TRACE [neovide::channel_utils] neovim_handler Flush
TRACE [neovide::editor] Image flushed
TRACE [neovide::editor] send_batch

About this issue

Original URL
State: open
Created 4 months ago
Reactions: 1
Comments: 17 (9 by maintainers)

Most upvoted comments

But I had no other choice than to merge it, since the reports of hangs were getting out of control, and I’m unable to reproduce it and therefore debug it myself. But we really need someone that can repeat the hangs to find the root cause and make a proper fix.

I think it was the right call, I went back to using neovim on the terminal for a while because I was getting those hangs every time I closed out of neovide.

Did some quick testing with the old code now and this is still the case on my machine. Closing out of neovide will trigger a stall every single time and leave the running neovim processes behind.

kareigu on Feb 28, 2024

@fredizzimo speaking of leaking processes, this was after one day of working:

(Yes, I open and quit neovide a lot, so that’s why I’m probably experiencing these issues more frequently than most.)

neovide didn’t hang while I was working yesterday, so as far as neovide was concerned, neovim told it to quit and neovide obliged, but then the neovim processes just stuck around. Haven’t had a chance to debug this yet.

sid-6581 on Feb 28, 2024