Android FF runs out of memory on opening the wasm (or even asm.js) pages in 
multiple tabs; so does the 32 bit firefox on windows. 
Chrome on android is multi-process and is able to open many tabs with wasm 
open simultaneously. 
Safari is magically able to open many tabs(with asm.js) - maybe it releases 
the memory of background tab.

Is it a design limitation of Firefox or is it possible to  work-around it 
in asm.js in some way?

-- 
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.

Reply via email to