To follow up on this, the problem went away when we disabled WASM, running on .js works fine. I do not think that our code does anything bad (as in non-standard pointer aliasing or bad alignment), and anyway my understanding is that the WASM code is more permissive to such bugs compared to Javascript. Is it normal to observe such a difference between WASM and Javascript? I mean, both work, it's just that the WASM version "Aw Snap"s after a few seconds, as if some watchdog kills it.
-- 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.
