Lower requested WASM memory for iOS user agents #26
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.
Description
🔗 Related Issue: o1-labs/o1js#823
This pull request addresses an issue where SnarkyJS applications encounter an
Out of Memory
error on iOS devices, specifically iPhones and iPads, while trying to initialize the WASM memory for plonk_wasm.js. This problem seems to be unique to iOS devices as desktop Safari doesn't appear to be affected.The solution involves modifying the maximum requested WASM memory for iOS user agents. Through testing, it's been found that these devices can handle up to 1GiB of requested memory. Attempting to request 2GB results in the same memory error. However, for all other user agents, the memory request remains unchanged, aiming for the maximum available, which is 4GiB.