Memory growth and asm.js in Chrome is a known issue: https://code.google.com/p/v8/issues/detail?id=3907
- Bruce Sent from my iPhone > On Aug 15, 2015, at 7:45 PM, Laurent Pugin <[email protected]> wrote: > > Setting "-s ALLOW_MEMORY_GROWTH=1" but without "-s TOTAL_STACK" and "-s > TOTAL_MEMORY" does not work. It crashes because of a memory allocation > failure. > > Now the interesting part is that adding "-s ALLOW_MEMORY_GROWTH=1" with "-s > TOTAL_STACK" and "-s TOTAL_MEMORY" works the same in Firefox but makes Chrome > at least twice slower the without memory growth enabled. Is this a known > issue? > > Also, looking more at the dynamic_cast issue, it seems that removing some of > them makes the code faster in Chrome but to a same proportion with Firefox. > So the speed difference is not (only) due to the RTTI. > > >> On Thursday, 13 August 2015 17:13:50 UTC+2, Laurent Pugin wrote: >> No, I'll try with memory growth enabled. Actually, I had tried with an >> earlier version of emsdk and it did not work at that time. >> >>> On Thursday, 13 August 2015 12:47:52 UTC+2, Bruce Mitchener wrote: >>> Do you have memory growth enabled to allow the heap resize? >>> >>> Sent from my iPhone >>> >>>> On Aug 13, 2015, at 5:38 PM, Guillaume Leclerc <[email protected]> >>>> wrote: >>>> >>>> I have the same issue in a physics project. The code is 3 times slower on >>>> chrome 43. >>>> >>>> Let me know if you find anything interesting. >>>> >>>> Guillaume Leclerc >>>> >>>> Le mardi 11 août 2015 14:33:23 UTC+2, Laurent Pugin a écrit : >>>>> >>>>> Hi, >>>>> >>>>> I am having troubles having asm compiled / running in Chrome. My C++ code >>>>> is compiled with the following emscripten options: >>>>> >>>>> -O3 --memory-init-file 0 \ >>>>> -s ASM_JS=1 \ >>>>> -s TOTAL_MEMORY=128*1024*1024 \ >>>>> -s TOTAL_STACK=64*1024*1024" >>>>> >>>>> In FireFox and IE Edge, I can see in the console the message the asm.js >>>>> is successfully compiled: >>>>> >>>>> 14:04:46.658 Successfully compiled asm.js code (total compilation time >>>>> 605ms; unable to cache asm.js in synchronous scripts; try loading asm.js >>>>> via <script async> or createElement('script')) >>>>> >>>>> However, nothing is shown in Chrome and I think it does not use asm since >>>>> it is then much slower. I have tested on Chrome Version 44.0.2403.130 >>>>> (64-bit) on Mac and also on Windows 10. Any idea how to double check if >>>>> Chrome does compile and run as asm? Or what is the issue if it does not? >>>>> Any flag to switch on as for IE Edge? >>>>> >>>>> Thanks in advance, >>>>> Laurent >>>> >>>> -- >>>> 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. -- 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.
