Swift tree-sitter parser causes plugin crash when loading .swift files

[rinOfTheStars]

Exactly what it sounds like. Presumably there's something seriously wrong with the version of tree-sitter-swift included in https://github.com/cursorless-dev/tree-sitter-wasms? From my understanding swift isn't a supported language yet either, so the best course of action is probably just to remove the parser until someone adds a newer, non-crashing one when adding proper swift support—I can make a PR for that tonight so a hotfix can hopefully be rolled out or something

[AndreasArvidsson]

What is wrong with it? I just tried to open a simple swift file with a hello world print statement and the parse tree worked fine. Do you have a code example that makes the parse tree crash? If so please share it so I can try myself.

[rinOfTheStars]

I wonder if it has something to do with iOS dev-specific code? I'll post the file that causes the crash later today

[rinOfTheStars]

Ok it's nothing wrong with the specific file, but seemingly with any token that means more than it just being plaintext—it works fine until I type class or struct at which point the crash-cycling occurs. Never mind, it happens even with plaintext, as long as there's more than one token—as soon as I hit space it crashes!

Is there any sort of crash log I can provide that Cursorless or VSCode produces?

According to the debug console, it seems to be caused by an out of memory error????
https://gist.github.com/rinOfTheStars/c9bfcb0342463b48d942b2e99fa37bfe

[rinOfTheStars]

...It works fine in the dev env. Regardless of if I'm using the main branch or the one where I removed the swift parser.

ಠ_ಠ

I can only assume this means something is royally fucked up somewhere in my VSCode install? Either way, seems its not an issue with vscode-parse-tree, so I'm closing this... and doing a clean reinstall of VSCode.

[rinOfTheStars]

...or not???? It crashes even in a fresh vscodium install! I can't reopen issues, but this might need to be reopened (or given an issue in the main repo)—is there a difference between how the cursorless or parse tree plugins are configured by default in prod vs in a development window?

[rinOfTheStars]

Got a friend of mine to replicate the bug on a Windows machine with a fresh install, reopening:

The question now is why it doesn't happen in dev environments, but that's secondary to getting a fix out

[AndreasArvidsson]

My bad. I completely forgot about the weird vscode behavior where it will crash in release, but work in develop. I have now confirmed that the parse tree crashes with swift files. This is a vscode bug and we already have a Cursorless issue regarding latex for this.
cursorless-dev/cursorless#2879

[AndreasArvidsson]

Pull request to disabled swift on newer vscode versions
#111

[rinOfTheStars]

Can confirm the fix is working!

[AndreasArvidsson]

Vscode issue https://github.Com/microsoft/vscode/issues/243747 is closed and released in vscode version 1.107.0.

Swift is now supported on parse tree extension 0.48.0
#124