Having devtools console open/closed to affect the issue sounds like IE11 is disabling optimizations when console is enabled. Safari does the same, and disables some JS optimizations when the console is opened. The large memory usage is probably related to one of their JS engine optimization passes. Though that is just a guess. You might try submitting a bug report to IE11 bug tracker, although the answer may just be "wait for Edge to launch".
2015-05-19 12:40 GMT+03:00 Dmitry Vitkovsky <[email protected]>: > Yes but I have another case: release build without devtools hangs the > browser. With devtools it's okay. > This is really strange. Maybe IE tries to enable some optimization when > devtools are closed and this optimization runs too long and consumes too > much resources? > I'll try to force disabling this optimization by adding top-level with or > try-catch. > > On Tuesday, May 19, 2015 at 11:57:48 AM UTC+3, Woof wrote: >> >> I had the same freezing issue with IE with debug builds of a similar >> size. With release builds, and not opening the developer tools at all, >> everything works fine (the application had plenty of testing and wasn't >> found to freeze otherwise). >> > -- > 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.
