You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Structured cloning of WebAssembly.Memory is not defined #2155
Just to clarify, this is only serializing/deserializing shared WebAssembly.Memory right? I don't think Gecko supports doing that for unshared memories. You could make a copy of the underlying ArrayBuffer if you want, but it's not transferable.
Technically the threads proposal hasn't merged yet, and so shared memory isn't defined here yet. I looked upstream though and it is missing a definition for this in the specification there.
Activity
eqrion commentedon May 7, 2026
Just to clarify, this is only serializing/deserializing shared
WebAssembly.Memoryright? I don't think Gecko supports doing that for unshared memories. You could make a copy of the underlying ArrayBuffer if you want, but it's not transferable.Technically the threads proposal hasn't merged yet, and so shared memory isn't defined here yet. I looked upstream though and it is missing a definition for this in the specification there.
annevk commentedon May 8, 2026
I created some tentative tests here to clarify what I mean and what I think the specification needs to require: web-platform-tests/wpt#59748.
Serialization & deserialization of WebAssembly.Memory
Bug 2038126 [wpt PR 59748] - Serialization & deserialization of WebAs…
Serialization & deserialization of WebAssembly.Memory
Bug 2038126 [wpt PR 59748] - Serialization & deserialization of WebAs…
Bug 2038126 [wpt PR 59748] - Serialization & deserialization of WebAs…
Bug 2038126 [wpt PR 59748] - Serialization & deserialization of WebAs…
Bug 2038126 [wpt PR 59748] - Serialization & deserialization of WebAs…