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.

Sign up for GitHub

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

Jump to bottom

VS Code: tree-sitter wasm bindings memory issue #3799

Open
valerybugakov opened this issue Apr 15, 2024 · 0 comments
Open

VS Code: tree-sitter wasm bindings memory issue #3799

valerybugakov opened this issue Apr 15, 2024 · 0 comments
Labels
clients/vscode cody

Comments

@valerybugakov
Copy link
Member

  • Tree-sitter WASM bindings usage causes V8 external memory to grow linearly with the number of documents parsed with no clear way to free it.
  • Unit test for reproduction TreeSitter memory leak repro #3788
  • Related GitHub threads: #1, #2, #3
  • I'm able to clean up the V8 external memory that grows in tests, but for that, I hacked a couple of changes into the pre-build tree-sitter WASM bindings. With them, I re-create a new parser instance after parsing 10k documents which allows GC to clean up the previously created WebAssembly.Memory instance
  • Slack thread.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clients/vscode cody
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pkukielka @valerybugakov @kalanchan