Post

Do you know what the linear memory GC overhead was? Either compared to GraalVM's normal GC, or the browser's? (I would expect linear memory GC to have more overhead in some ways - e.g. stack scanning - but also the chance to use VM/language-specific low-level tricks)

I remember longer stop-the-world GC pauses in our simple GC implementation, and leakage issues related to JS interop. I didn't work on that back then, can check with the team for details.