Describe the bug
After a working on a project..for a sufficiently long time, i'd say 15 minutes or more, too many files open issue starts popping up. I dont get this issue while using neovim in terminal.
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Please run neovide --log and paste the contents of the .log file here:
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:39:34: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:40:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:41:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:42:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:43:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:44:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:45:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:46:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:47:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:48:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: too many errors
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: failed to parse file
Ignored client type property: "methods"
Ignored client type property: "attributes"
thread 'tokio-runtime-worker' panicked at 'Focus Gained Failed: NeovimError(Some(0), "Vim(call):E903: Process failed to start: too many open files: \"/usr/bin/sh\"")', src/bridge/ui_commands.rs:114:18
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Additional context


After pressing enter, the error dissappears, and if try to write using :w after it, error popups up again..more severly


This seems like an upstream issue. But theres some things that would help to isolate it:
Can you remove gitgutter and see if you can reproduce the issue??
Can you remove gitgutter and see if you can reproduce the issue??
I tried removing git gutter, but the same kind of error pops up for a different plugin. I will remove git gutter for the day and try to reproduce the issue.
@Kethku
neovide -- --cleanerror i got that crashed neovide..multiple times..reproducible everytime
@Kethku
Ignored client type property: "methods"
Ignored client type property: "attributes"
Ignored style attribute: "fg_indexed"
Ignored style attribute: "fg_indexed"
Ignored style attribute: "fg_indexed"
Ignored style attribute: "fg_indexed"
Ignored style attribute: "fg_indexed"
Ignored style attribute: "fg_indexed"
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 4, kind: Interrupted, message: "Interrupted system call" }', /home/smit/.cargo/git/checkouts/winit-cdba476763ae8f28/3b5462e/src/platform_impl/linux/x11/mod.rs:396:54
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace