Memory issue when opening a .tex file with the parse tree extension enabled

[pkozlows]

Working in VSCode, with Latex Workshop disabled, before I enable the Pokey parse tree extension, when i have a .tex file open, I have the clean log, but once I enable Parse Tree extension, ONLY when I have a .tex file open, I get the log with errors.

clean.log

errors.log

[pkozlows]

Operating System: MacOS 15.3.1

Visual Studio Code Version:
Version: 1.98.2 (Universal)
Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin arm64 24.3.0

LaTeX Workshop Version: 10.9.0

TeX Distribution Version: TeX Live 2024)

[pkozlows]

Let me know if there is any additional information I could supply to make this clearer!

[AndreasArvidsson]

I've looked into this and I think it's a problem with the latex Tree sitter wasm we are using. I'm currently in the process of updating our parse tree extension and how the wasm binaries are built. Once that is done I will try a newer latex parser.

[pkozlows]

Do you think you will be able to look into this soon?

[AndreasArvidsson]

I've made multiple attempts to build the wasm files in CI, but unfortunately I'm still running into problems. It's an ongoing process, but I don't have an eta.
https://github.com/cursorless-dev/tree-sitter-wasms

[AndreasArvidsson]

Finally I got it working!
In this pull request the latex parse tree is updated. I'm not sure this is going to solve the problem, but let's give it to try.
cursorless-dev/vscode-parse-tree#103

[AndreasArvidsson]

Looks like updating the latex parse tree didn't help. This is really weird and hard to debug. When I'm debugging the vscode-parse-tree extension latex works fine, but when running it in "production mode" we get a memory crash. I've also tried to update to the latest version of web-tree-sitter, but the problem persists. Looks like there is a memory problem inside of the Tree sitter latex parser and I'm running out of ideas to try to fix it.

[pokey]

have we filed something upstream with tree-sitter-latex?

[AndreasArvidsson]

No. Not yet.

[AndreasArvidsson]

I'm not sure how to file this. On vscode version 1.96.4 latex works fine. Is it a vscode bug? A web-tree-sitter bug? A tree-sitter-latex bug?

[pokey]

strange. maybe worth looking around on vscode issues to see if there's any recent ones that seem related. If not, maybe worth filing with VSCode? The fact that downgrading vscode fixes it means it might be something for them?

[AndreasArvidsson]

I'm leaning towards that as well. I'm wonder if this could be related to the crash we have in ci for later vscode versions.

[AndreasArvidsson]

Issue filed with vscode

microsoft/vscode#248637

[AndreasArvidsson]

And the issue was closed immediately. At this point maybe we need to look for another latex parser or just disable latex from Cursorless. Being able to use the text base scopes must be better than having everything crash?

[pkozlows]

The downgrade of vs code has been a good workaround for me. if cursorless stops supporting latex will that mean that the latex scope types no longer get recognized for latex workshop? I don't think that would be a good thing.