-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neovim is stuck a 100% CPU #77
Comments
Hmm, strange. NimLSP just appears to be waiting for more requests. Do you see NimLSP consuming a lot of CPU when this happens? It might be a neovim or neovim/NimLSP interaction that just causes it to hang somehow. |
When the bugs occurs, it's the process nvim that gets stuck at 100% CPU, nimlsp is fine. I tried 2 different LSP Client (neoclide/coc and prabirshrestha/vim-lsp) and 2 different Nevoim version (latest devel and 0.4.3), with the same result |
Running neovim-nightly on Linux x64, using |
Here is what I do that reproduce :
Sometimes I have to repeat the last 2 step once before triggerring it. This is on NVIM v0.5.0-dev+1176-g94381310c2. I'll update to the new nightly NVIM v0.5.0-dev+1227-gb518b9076 and test again but I had the same result with v0.4.3 and v0.4.4. I'm using OpenSuse Leap 15.2 and use nvim.appimage. Opening non-Nim file (tried .jl, .cpp, .py files) do not have any issue. Edit with new nightly : NVIM v0.5.0-dev+1227-gb518b9076
|
Ah yes, can reproduce, after writing the |
Might be syntax highlighting, I used |
Could be, as writing |
I'm using https://github.com/alaviss/nim.nvim for syntax highlighting, if I use |
I use |
Same result as @zetashift I use |
That probably makes this a |
I created alaviss/nim.nvim#41 |
When opening a Nim file with Neovim, it gets stucks at 100% CPU after the file is opened for a while. Some action (?) will trigger the bug instantly (inserting "{" will do that for instance).
The bug happpend when opening the file https://github.com/SciNim/flambeau/blob/master/flambeau/raw_bindings/tensors.nim
Here is the log when using nimlsp in debug mode :
Once the bug occurs, I can only kill neovim with SIGINT .
The text was updated successfully, but these errors were encountered: