Sounds like this was a graphics driver issue. Though to second Alon's
voice, the thrown exceptions that are just numbers generally come from C++
throw statements inside asm.js code. Build with -O0, or with -g2,
--profiling or --profiling-funcs to get the browser report a good
callstack, and check the stack trace of the exception message.
Sometimes I have noticed that the trace presented in the exception message
is not very good, and it refers to a catch() {} block that has captured the
exception and e.g. rethrown or printed it. In that case, I generally just
comment out that try {} catch{} to let the exception raise up to browser
completely uncaught, which does seem to give better callstacks to point out
exactly where the throw statement occurred.
2016-04-21 0:51 GMT+03:00 thp069 via emscripten-discuss <
[email protected]>:
> The dependency on a newer graphics driver version may be overriden by
> about:config -> webgl.force-enable
>
>
> --
> 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.
