Thomas Vigouroux

After some investigation, and debugging, it seems that we are exceeding the match limit (the call to `did_exceed_match_limit` is returning 1).

Now that you say it is a bug, we get a strange SEGFAULT in approximately the same region, when using queries : https://github.com/neovim/neovim/issues/14369

Any update on this problem ? Can we help in any way, or is there any ressource for contributing and attempt to fix this ?

I don't know if this still exists, but anyway, this should move to the `nvim-treesitter-texobjects`.

Nice work in profiling this. I'll try to look into it when I have time.

Working on it then. I think this can be marked as a bugfix for 0.5

Reopenning after https://github.com/nvim-treesitter/nvim-treesitter/issues/1708, I think I found a fix for that, by using the new api function added in #15248 and some optimizations in `TSHighlighter:on_line`

In `nvim` master, holding the escape key for too long results in : ``` nvim: ../src/nvim/tui/input.c :609 : handle_raw_buffer: assertion « consumed read_stream.buffer->size » failed. ```

@theHamsta, that's really weird that the queries ignore `@_foo`, does that also happens in the playground ?

> Why remove the state between lines? That seems like a pure regression from a performance perspective (also it just is wrong, we redraw a line range, not a line...