While working on taking advantage of Memory.toResizableBuffer in #27096 I came across what looks like might be a bug in Firefox.
As far as I can tell, for some reason, calling toResizableBuffer on the shared WebAssembly.Memory object causes the initial postMessage to new workers (the message that contains the memory object) so silently fail.
The bug only seems to occur with shared wasm memory object and only when they have toResizableBuffer called on them.
While working on taking advantage of
Memory.toResizableBufferin #27096 I came across what looks like might be a bug in Firefox.As far as I can tell, for some reason, calling
toResizableBufferon the sharedWebAssembly.Memoryobject causes the initial postMessage to new workers (the message that contains the memory object) so silently fail.The bug only seems to occur with shared wasm memory object and only when they have
toResizableBuffercalled on them.