[WASM] change wasm initial memory to 100MB, allow memory increase #2575
Conversation
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
halx99
reviewed
Jun 23, 2025
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.
With EMSCRIPTEN, the
INITIAL_MEMORYis the amount of bytes that will be required at launch in the browser no matter it is needed or not, and the app won't be able to ask for more than this amount too. While it works on high performance devices, it won't on medium or low devices because they don't have that much memory.The solution is to lower the initial value (to 100MB which seems reasonable), and allow the memory to grow by using
ALLOW_MEMORY_GROWTH.Note: it will be allowed to grow until
MAXIMUM_MEMORYwhich is 2GB by default