webassembly.api.Memory.Memory - Document the compatability status of 4GB heap
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Missing compatibility data
What information was incorrect, unhelpful, or incomplete?
WebAssembly added support of 4GB heap after https://github.com/WebAssembly/spec/issues/1116, but the compatability status is not documented.
What browsers does this problem apply to, if applicable?
Firefox, Safari, Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
Compatability status of browsers found yet:
- Chrome 83 https://v8.dev/blog/4gb-wasm-memory
- Firefox 89 https://bugzilla.mozilla.org/show_bug.cgi?id=1676441
- Safari 15.2 https://webkit.org/blog/12140/new-webkit-features-in-safari-15-2/
Did you test this? If so, how?
Build a wasm binary that can allocate memory, with MAXIMUM_MEMORY=4GB, and grow pages to 65536
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
- Chrome 83 https://v8.dev/blog/4gb-wasm-memory
- Firefox 89 https://bugzilla.mozilla.org/show_bug.cgi?id=1676441
- Safari 15.2 https://webkit.org/blog/12140/new-webkit-features-in-safari-15-2/
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/WebAssembly/Reference/JavaScript_interface/Memory/Memory
MDN metadata
MDN page report details
- Query:
webassembly.api.Memory.Memory - Report started: 2025-09-08T07:42:13.733Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the MDN WebAssembly Memory constructor page and the browser compatibility data entry it represents. Compare the linked Chrome, Firefox, and Safari references with the existing compatibility records; done means the 4GB heap support status is documented for the reported browsers and the data validation passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100