Lazyvim - neovim crash when closing chat buffer #1448
Replies: 27 comments 39 replies
-
what does |
Beta Was this translation helpful? Give feedback.
-
Also if neovim closes itself with "strange view" that most likely means that neovim crashed. maybe some treesitter crash? But sounds very unreated to the actual plugin |
Beta Was this translation helpful? Give feedback.
-
Hi @deathbeam Sorry I forgot to explain it. This is the lazyvim default to close a window, which worked perfectly before to close the panel. I tried to use "q" too, as the "gh" command suggests. But it only works the first time (if I open the "gh" command first, for example). If I open the panel and try to close it, the error occurs (without any error message tho) |
Beta Was this translation helpful? Give feedback.
-
Do you have anything like vim._extui enabled or old treesitter parsers or old neovim version? Also can you try this with other markdown buffers? Also can you try reproducing it by cloning this repo and running |
Beta Was this translation helpful? Give feedback.
-
Hi @deathbeam Thanks for the help! I have the default Lazyvim config, with some extra plugins in the plugins folder and some keymaps of my own. So I don't think ive old parsers or anything, since this worked a few weeks ago. I will try to reproduce it cloning this repo into a clean folder and run the command you wrote. Thanks! |
Beta Was this translation helpful? Give feedback.
-
It looks like cloning the repo and starting Neovim with Do you have any idea? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Well can you try other markdown buffers and see if you get the crash? That have treesitter enabled. As the biggest thing that changed here is that the plugin started relying on treesitter more. But not sure if anything changed on LazyVim side. For example it could be because of extui as well as I said as its pretty unstable. Can you also post output of And vim._extui needs to be specifically grabbed via EDIT: Also can you do |
Beta Was this translation helpful? Give feedback.
-
I created a
But if I run it a second time, Neovim crashes as when I try to close the copilot panel chat.
I will try now with the minimal config |
Beta Was this translation helpful? Give feedback.
-
Minimal config
|
Beta Was this translation helpful? Give feedback.
-
I see on my |
Beta Was this translation helpful? Give feedback.
-
Yea it looks like you might have some old treesitter parsers from nvim-treesitter probably. I think lazyvim was switching to |
Beta Was this translation helpful? Give feedback.
-
@deathbeam Yeah maybe, I did not notice it before. Do you know if its the |
Beta Was this translation helpful? Give feedback.
-
i would delete both and then try :TSUpdate again. it will redownload what it needs. And the one tht is not crashing is the built in one e.g the lib/nvim one |
Beta Was this translation helpful? Give feedback.
-
Deleted the whole treesitter and reinstalled again. The error persists... |
Beta Was this translation helpful? Give feedback.
-
and what is the result of the checkhealth now for vim.treesitter? |
Beta Was this translation helpful? Give feedback.
-
I see bunch of crash reports here as well so maybe its related. Also macOs related ones: https://github.com/nvim-treesitter/nvim-treesitter/issues?q=crash |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Weird, but they are all closed. I could try to install lazyvim again or something, but I don't think this is the problem. |
Beta Was this translation helpful? Give feedback.
-
I tried also deleting the parsers in Still crashing |
Beta Was this translation helpful? Give feedback.
-
Well they are closed but without resolution really, the latest one was converted to discussion: nvim-treesitter/nvim-treesitter#8114 The parser being somehow wrong is definitely the issue in this case I think, but im not sure why its coming back after reinstall of the parsers. |
Beta Was this translation helpful? Give feedback.
-
Thanks, This is really driving me crazy |
Beta Was this translation helpful? Give feedback.
-
Hmm can you maybe try doing what the guy did in that discussion? e.g try adding the nvim-treesitter instal to the minimal.lua script as well and see if you can reproduce it |
Beta Was this translation helpful? Give feedback.
-
Alternatively just adjust your treesitter config so it wont install the markdown parser as neovim has its own built in one that should work to workaround the issue for now (but you might run to crashes elsewhere with broken parsers potentionally). or check if nvim-treesitter doesnt have some parser build cache somewhere maybe (can try deleting the nvim-treesitter completely if its cached somewhere and try to make lazyvim download it again, while also clearing all cache files at same time) |
Beta Was this translation helpful? Give feedback.
-
@deathbeam I did that. I deleted the whole treesitter. I am not sure how I can make treesitter to not download the markdown parser tho, but it could be an option. Thanks! |
Beta Was this translation helpful? Give feedback.
-
require'nvim-treesitter.configs'.setup { probably adjusting the ensure_installed and removing markdown and markdown_inline (not sure if thats possible in LazyVim but should be) |
Beta Was this translation helpful? Give feedback.
-
For now converting this to discussion as I dont think there is something that can be fixed on plugin side at least |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check docs and existing issues?
Neovim version (nvim -v)
0.11.4
Operating system/version
macOS 26
Describe the bug
Hello!
I’m not sure when this started, but it’s a bit annoying. I haven’t found anything in the plugin repository about this. When I open a new Copilot Panel with
<leader>aa
and try to close it in normal mode with<leader>wd
, Neovim closes itself, but the view looks strange (see screenshot). I have to close the buffer and then the windows to close the panel.Steps To Reproduce
<leader>aa
<leader>wd
Expected Behavior
I expected the Copilot window to close as it always did.
I posted this on the Lazyvim repo too, but Folke says he did not change anything in the config, so it maybe is related to the plugin itself?
I can close any other window with the same shortcut without a problem.
Beta Was this translation helpful? Give feedback.
All reactions