Kræn Hansen

This is still an issue.

This is still an issue.

This is still an issue.

I've pinged @bcoe on X .. we're also experiencing #1535 (or likely a variant thereof).

Another reproduction: ``` npm install [email protected] segfault-handler npx nyc -- node -e 'require("segfault-handler").causeSegfault()' ```

> relying on the GC to kick in and eventually collect the Realm instance and free up the callback? Exactly, GC would free the Realm instance, which would ultimately free...

We should wait for TypeScript-first models to land before fixing this, as it introduce a `Realm.Types` namespace where the BSON types will be available.

@liamjones thanks for sharing this! Reading the document, I see that the proposal will still use the Chrome DevTools Protocol (CDP) and therefore JS code will still be executing on...

@liamjones no worries. Although we try to engage with the community and stay on top of these things ourselves, it was really good that you brought it to our attention...

@kelset we're still seeing this on RN 0.71.0 (just tested with 0.71.0-rc.5 from [our `bindgen` branch](https://github.com/realm/realm-js/tree/bindgen) which doesn't have the workaround we mentioned above).