Unfortunately, I'm already using Oz with the --profiling setting to enable some simple debugging. Are there ways to work around this issue?
On Thursday, March 3, 2016 at 2:40:29 AM UTC+8, Alon Zakai wrote: > > Yes, you're hitting a limitation of Chrome's JS engine. > > Is that on a fully-optimized JS? I've seen this on -O0 and -O1 builds on > Chrome, but -O2 and above should be ok (if not, we need to look into a > workaround). > > On Wed, Mar 2, 2016 at 2:12 AM, awt <[email protected] <javascript:>> > wrote: > >> Hi, >> >> I was trying to open my application on Chrome which is quite large and I >> encountered the following error: >> >> "Uncaught RangeError: Maximum call stack size exceeded" >> >> The console showed that the error happened at the following line: >> >> var asm = (function(global,env,buffer) { >> >> Can I assume that the error occurs because the size of my asm.js file is >> just too large and that the only way to get it to run on Chrome is to >> reduce the JS size? My application runs fine on Firefox by the 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 [email protected] <javascript:>. >> 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.
