memory-control
memory-control copied to clipboard
A proposal to introduce finer grained control of WebAssembly memory.
This issue tracks discussion of the **`virtual` mode** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal document](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/virtual.md).
This issue tracks discussion of the **`maplength`** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal document](https://github.com/WebAssembly/memory-control/blob/main/proposals/memory-control/maplength.md).
This issue tracks discussion of the **static memory protection** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal...
This issue tracks discussion of the **BYOB for WebAssembly.Memory** sub-proposal. This proposal is one possible component of the eventual Memory Control MVP. Please make sure to read the [full sub-proposal...
Placeholder issue to address the question of stream APIs on the web, and how they would integrate with this proposal. (See https://github.com/WebAssembly/memory-control/pull/12#discussion_r1621301910.) @dtig, feel free to edit this comment into...
## Introduction and Context There have been a number of conversations and questions raised about the possibility to share subsets of memory between multiple WebAssembly instances and the host environment....
(I'm a little late to the party here and not proposing immediate work on this, but I thought it'd still be useful to have an issue to collect discussion and...
JITting emulators like http://copy.sh/v86 incur significant overhead from having to check page tables on every memory access. Traditionally, emulators implement this by trapping SIGSEGV. The signal handler isn’t necessary, however....