Not sure what could cause that problem. What flags are you using in that compilation? Things like files etc. may touch memory, perhaps we have a bug there.
On Mon, Mar 26, 2018 at 2:53 AM, Kasper Peeters <[email protected]> wrote: > My code works fine on Chrome/Firefox/Edge when built with WASM=1. I am now > trying to make it run in IE11 as well, for which I cannot use the default > native wasm. So I added BINARYEN_METHOD='interpret-binary' to my build > for IE11. Unfortunately, this makes the code bail out at the very start with > > Assertion failed: area for memory initializer should not have been > touched before it's loaded. > > (on IE11 but also on Chrome/Firefox/Edge). > > Any suggestions? Thanks! > > Kasper > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
