In that case, I think you may need to set MAXIMUM_MEMORY to 4GB, or to -1, so that it is compatible with your manually-created memory.
What I think might have changed here is that emscripten now sets the default MAXIMUM_MEMORY to 2GB. That is because not all VMs support 4GB yet, and also since to support more than 2GB we need to increase code size a little, so we don't want that by default. On Fri, Jun 5, 2020 at 6:18 PM Soeren Balko <[email protected]> wrote: > 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 > <https://groups.google.com/d/msgid/emscripten-discuss/a9b94bf6-97b7-49cd-9d63-92cc9f730f1co%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAEX4NpT9YS%3DBkyQBDXmrDgkgGhSytoR870YYTtNrAJhv8PgySg%40mail.gmail.com.
