Chrome has had a longstanding bug that if one allocates a too large ArrayBuffer (or WebAssembly.Memory) that the page does not have enough memory, the page can Aww snap instead of throwing a JavaScript exception. I don't know if that is the cause here, but you could try allocating a much smaller size for TOTAL_MEMORY to see if that might avoid the issue.
2017-09-19 21:36 GMT+03:00 Gaurav Dewan <gauravdewan...@gmail.com>: > On redmi note 4 4gb ram chrome canary and stable latest crashes with Aw snap > on opening any medium sized webassembly like > Websighjs > FF works fine on same device. > Maybe Chrome thinks there is less memory on mi environment > Is Aw snap in webassembly common issue on Android Chrome ? > Logged > https://bugs.chromium.org/p/chromium/issues/detail?id=766666 > > -- > 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 emscripten-discuss+unsubscr...@googlegroups.com. > 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 emscripten-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
