Extension host crashes on `unhandledRejection`
See original GitHub issueThis issue is mostly FYI
vscode-tree-sitter crashes the extension host process in case of any unhandled promise rejections. Unfortunately, you are not able to do much on the extension side. Most likely the culprit is your web-tree-sitter dependency. The related issue is https://github.com/tree-sitter/tree-sitter/issues/571#issue-577509898.
At the end of the day vscode-tree-sitter damages the extension host process when this happens and all other extensions altogether.
The initial issue was reported in https://github.com/rust-analyzer/rust-analyzer/issues/3515#issuecomment-596207493 to the unrelated rust-analyzer repo.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:22 (1 by maintainers)
Top Results From Across the Web
Live Sass Compiler causing Extension Host crash after latest ...
I am trying to use sass styling and Live Sass Compiler extension, I recently installed it and now keep getting a extension host...
Read more >Node.js v19.3.0 Documentation
js handle objects with undocumented APIs. Using any functions or properties on the object is likely to crash your application and should be...
Read more >Error Messages | Cypress Documentation
If the browser running Cypress tests crashes, currently, Cypress will abort ... or its unhandledrejection handler, Cypress will detect it and fail the...
Read more >Electron Releases - GitHub Pages
Fixed query string parsing in PDF Viewer #10008; Fixed crash that occurred ... getExtensions to add/remove/get Chrome extensions in an Electron app #9918 ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

May be it’s this one?
https://github.com/EvgeniyPeshkov/syntax-highlighter
I recognize the author from this discussion.
One other thing to note, there seems to be another extension (I believe it’s called syntax highlighter) that uses the tree sitter, but seems to be actively maintained. It might be worthwhile to switch to focusing on that repo.
If you copy the commands, resources, and settings folder into a fork of that actively maintained repo the
commands/startwill most likely still work and autoinstall the node-gyp dependencies of that repo. The compile command might be different, but I’m sure they’d have an npm script for it