Skip to content
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

/usr/share/vis/lexer.lua:1256: backtrack stack overflow (current limit is 400) #1218

Closed
acidrums4 opened this issue Dec 4, 2024 · 3 comments

Comments

@acidrums4
Copy link

Problem

For some reason unknown to my pretty void programming knowledge, when going past a certain number of lines on
the uncompressed attached file (moving with Ctrl+F, arrows, paragraph, you name it - about the line 500 or something), vis crashes/freezes completely and throws this error:

/usr/share/vis/lexer.lua:1256: backtrack stack overflow (current limit is 400)

Can't tell if this is something related about a plugin or what (I'm just using the 'vis-pairs' plugin). Maybe it's something about the lexer thing you guys talked about at #1198?

The really weird thing about this is that it's happening only and only with this file. Not sure what it has that triggers this error.

Steps to reproduce

  1. Open the uncompressed attached file, say `vis _cpu-quick-compare.php'
  2. Go past the 500th line, or the end of file with G

vis version (vis -v)

vis 0.9 +curses +lua +tre +acl

Terminal name/version

konsole 24.08.3

$TERM environment variable

xterm-256color

@fischerling
Copy link
Contributor

Upstream has increased the stack size in orbitalquark/scintillua@f1375d3.
We should probably resync our lexers once again.

@mcepl
Copy link
Contributor

mcepl commented Dec 27, 2024

I have proposed that three months ago in https://lists.sr.ht/~martanne/devel/patches/55179, but I have been ignored as usual. I have these commits included in https://git.sr.ht/~mcepl/vis/log as https://git.sr.ht/~mcepl/vis/commit/7bdc1c65e32e5639bd321992c598353eccbce1e6, and it seems to work just fine.

@rnpnr
Copy link
Collaborator

rnpnr commented Jan 6, 2025

Should be fixed by 603bc09.

@rnpnr rnpnr closed this as completed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants