I was seeing this just the other day but another Chrome version rolled in pretty quickly and the issue went away... what version of Chrome are you testing with?
On Wed, Feb 20, 2019 at 9:34 PM <[email protected]> wrote: > Wait, nevermind, that was just my printf debugging not getting flushed > before the crash. > > OK, so I have this complicated function (a decompression function) that > runs on all the other browsers (and ran in older Chrome versions), but now > just crashes. What's the best way to debug this? Printf doesn't seem > reliable, since it dies before output (I guess I could try a fflush(stdout > );). > > Is there any logging I can compile with or anything? > > > On Wednesday, February 20, 2019 at 6:17:54 PM UTC-8, > [email protected] wrote: >> >> First function in main(), dies with a "Aw, Snap! Something went wrong >> while displaying this webpage." error. >> >> Runs fine in Firefox, Edge, and Safari - what's the best way to track >> this down? >> > -- > 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.
