dtig / memory-control Goto Github PK

Since one of the intended uses of this is for ArrayBuffers, I am wondering about the performance (and predictability) implications of using mapping operations on buffers whose sizes are not a multiple of a page size (and indeed may be smaller than a page). What is supposed to happen if you access past the end of a mapped buffer?

At one point I had envisioned a set of memory instructions that accepted an object pointer and performed bounds checks (WebAssembly/gc#109). Do you imagine that these mapping instructions would be able to take the place of those?

I haven't been learning WASM for long, but I find that wasm memory now has no way to manage constant data (and ohter kinds of data)，overwriting this data may cause security problems, and unmanaged memory even causes buffer overflows.

So I am glad to find this proposal. I think it’s necessary to manage wasm memory. I think that sometimes it is necessary to mark read-only buffer and the data owner(for example, if there is multiple memory, a mod can have its own memory, and other mods cannot access the data in that memory), even though there is additional overhead. Some of the content in the program itself is immutable, and managing the ownership of the data can also be convenient for some security applications.

In addition, I am currently a student and have a great interest in wasm memory management , so I would like to ask where I can learn more details and progress on this proposal (I would even like to take it as my graduate research direction if possible, and I would be very grateful if you could tell me some of this information).

Filing an issue to track the discussion from the design issue - WebAssembly/design#1439 (comment)