fix: various memory issues#35
Merged
vahidlazio merged 4 commits intomainfrom Oct 2, 2025
Merged
Conversation
vahidlazio
approved these changes
Oct 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The allocator we were using (wee-alloc) is old, unmaintained and has memory leaks. This PR switches to the default wasm32-unkown-unkown std allocator. The switch strangely broke the JS and GO test apps. It turned out that what we thought were commands to read from a buffer, were in reality views into the underlying memory which we subsequently freed! The new allocator must be more aggressively reusing or zeroing the memory which helped uncover these bugs.