i'm observing the death of node processes and occasionally vscode extension debug launched windows. one commonality is the use of the wasm bindings for tree-sitter. i'm now trying to rewrite some bits using the node bindings instead. so far the node process deaths have not been reproduced, so it may be a web-tree-sitter (wasm-bindings) thing. perhaps this is an opportunity to measure some performance differences between the two...

with the node bindings, the node process doesn't die, but the parser seems to become null occasionally (also observed for the wasm bindings).

on a side note, it appears maxbrunsfeld (creator of tree-sitter) is no longer on the atom editor dev team. https://github.com/tree-sitter/node-tree-sitter/issues/57#issuecomment-589379300