OK, so turns out that the issue was that we construct the
WebAssembly.Memory outside the Emscripten-generated code and without the
("maximum") property set in the constructor. We do so in order to be able
to re-use the same WebAssembly.Memory instance across multiple subsequent
WebAssembly instances.
The "maximum" property used to be optional - is it no longer?
Soeren
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/a9b94bf6-97b7-49cd-9d63-92cc9f730f1co%40googlegroups.com.
