Freeze in large C file with treesitter

[zeertzjq]

Is your feature request related to a problem? Please describe.
When treesitter highlighting is enabled, vim-matchup unconditionally uses treesitter delim skip, which can be very slow. In some large C files this causes vim-matchup to freeze Nvim for seconds when moving cursor onto a curly brace, and the following change makes the lag disappear:

diff --git a/autoload/matchup/loader.vim b/autoload/matchup/loader.vim
index e78243b..b943f7a 100644
--- a/autoload/matchup/loader.vim
+++ b/autoload/matchup/loader.vim
@@ -58,12 +58,7 @@ function! matchup#loader#init_buffer() abort " {{{1
   let b:matchup_delim_re = s:init_delim_regexes()
 
   " process b:match_skip
-  if l:has_ts_hl
-    let b:matchup_delim_skip
-          \ = "matchup#ts_syntax#skip_expr(s:effline('.'),s:effcol('.'))"
-  else
     let b:matchup_delim_skip = s:init_delim_skip()
-  endif
 
   " enable matching engines
   let b:matchup_active_engines = {}

Describe the solution you'd like
Add an option to vim-matchup to disable treesitter delim skip.

[andymass]

Because it uses the Treesitter AST, my expectation is matchup#ts_syntax#skip_expr would be very fast. (At least faster than vim syntax highlighting.) Maybe there is something wrong in the way it's computed or cached.

Can you provide a sample C file which has the issue?

[zeertzjq]

src/nvim/regexp_nfa.c in Nvim source code.

[zeertzjq]

I may have made a mistake when testing this. It seems that when I fully enable matchup treesitter support (matchup = { enable = true }), vim-matchup freezes Nvim every time viewport scrolls by a screen. However, if I disable that (matchup = { enable = false }), vim-matchup only freezes the first time I stop cursor on a curly brace and is fast afterwards. This is probably not needed then.

[andymass]

Still seems a bug. The promise of treesitter is that things are blazing fast. I will investigate nevertheless.

…

On Wed, Jul 5, 2023, 11:10 AM zeertzjq ***@***.***> wrote: I may have made a mistake when testing this. It seems that when I fully enable matchup treesitter support ( matchup = { enable = true },), vim-matchup freezes Nvim every time viewport scrolls by a screen. However, if I disable that ( matchup = { enable = false },), vim-matchup only freezes the first time I stop cursor on a curly brace and is fast afterwards. This is probably not needed then. — Reply to this email directly, view it on GitHub <#302 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSY3DKWZBSJ2EVUX7KUWIDXOV7WDANCNFSM6AAAAAAZ6MLRCU> . You are receiving this because you commented.Message ID: ***@***.***>

[andymass]

I see a huge amount of lag in regexp_nfa.c when scrolling but it doesn't seem to be caused by ts syntax skip but instead this call to get_active_nodes

vim-matchup/lua/treesitter-matchup/internal.lua

Line 221 in 3c4ccc4

local active_nodes, symbols = unpack(M.get_active_nodes(bufnr))

When I comment this line out the lag disappears. What I don't understand is that get_active_nodes is gated behind ts_utils.memoize_by_buf_tick

vim-matchup/lua/treesitter-matchup/internal.lua

Line 95 in 3c4ccc4

M.get_active_nodes = ts_utils.memoize_by_buf_tick(function(bufnr)

Yet when scrolling it seems to be called again and again, even if the buffer hasn't changed.

[3rd]

Had this same issue but in Lua files, when moving cursor up/down and hitting a bracked it would freeze the editor for a bit (on a very beefy machine), fixed by disabling the plugin. Might be a Neovim issue, disabled Navic as well for the same reason.