NeoVIM Crashing when Scrolling Files w/o Error Message about nvim-treesitter-context HOT 12 CLOSED

Can't help without a stacktrace. Sorry

from nvim-treesitter-context.

https://github.com/neovim/neovim/wiki/FAQ#backtrace-linux

from nvim-treesitter-context.

Look at the link provided by @wookayin

from nvim-treesitter-context.

Sorry, this isn't something we can help with here. My guess is this is related to the built parser objects being corrupt in some way.

from nvim-treesitter-context.

And there's nothing I can do to fix this? Do I have to live without treesitter-context now? 🥺

from nvim-treesitter-context.

Not if you don't know how to properly debug this.

Ts-context is just using normal treesitter APIs. If usage of those API's causes a crash, then an issue lives in the implementation behind those APIs, not the application.

Ts-context just found a codepath to trigger a bug, but there is no bug in ts-context itself.

What I would do would be to reduce this problem as much as possible. That includes reducing down the logic in ts-context until you have a minimal testcase (0 plugins). Obviously this is difficult and time consuming.

But like I said, this is likely caused by incorrectly built parsers. You'll be able to find out more if you can get a stacktrace of some kind.

from nvim-treesitter-context.

Stacktrace please. However this is likely not an issue with this plugin.

Crashes should be reported to neovim core with a stacktrace.

from nvim-treesitter-context.

For me the only solution was to uninstall treesitter-context, not had a single crash since then.

from nvim-treesitter-context.

I'm facing the same issue too:

from nvim-treesitter-context.

Can't help without a stacktrace. Sorry

I tried to log everything, but the crash is happening and no logs are been generated

from nvim-treesitter-context.

Can't help without a stacktrace. Sorry

If you give us some way to generate, I will be happy to try

from nvim-treesitter-context.

I have the same issue, and I have the following logs from running with

vim.cmd("set verbosefile=~/nvim.log")
vim.cmd("set verbose=15")
vim.cmd('let $NVIM_LOG_FILE = expand("~/nvim.log")')

logs:

... <- successful logs
                                                                                                      Error executing vim.schedule lua callback: ...vim-treesitter-context/lua/treesitter-context/render.lua:68: 'height' key must be a positive Integer
                                                                                                      stack traceback:
                                                                                                      	[C]: in function 'nvim_win_set_config'
                                                                                                      	...vim-treesitter-context/lua/treesitter-context/render.lua:68: in function 'display_window'
                                                                                                      	...vim-treesitter-context/lua/treesitter-context/render.lua:337: in function 'open'
                                                                                                      	.../lazy/nvim-treesitter-context/lua/treesitter-context.lua:50: in function 'open'
                                                                                                      	.../lazy/nvim-treesitter-context/lua/treesitter-context.lua:111: in function <.../lazy/nvim-treesitter-context/lua/treesitter-context.lua:92>
... <- cleanup logs

I don't know why it's indented, it's outputted like that.

Note: I use lazyvim - don't know if that helps with anything.

Neovim version: 0.9.4, mac m2, running nvim-treesitter-content on head dbcd938 I had this issue.

@lewis6991 let me know if you need more info

from nvim-treesitter-context.