[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] shader compilation hangs/crashes

Thanks for the reports.

Please note that in Chrome's bug database, the people working on WebGL
don't see the initially filed bugs from end users. Please inform us
directly about issues you file so that we can tag them appropriately.
Otherwise they can slip through the cracks during the triage process.

It's not a fair statement to say that UAs don't care about shader
compilation issues. On the contrary, many of the tests in the WebGL
conformance suite came from developers who ran into shader compilation
or evaluation problems on one platform or another. Wherever possible,
workarounds have been added to implementations, and these reports have
often resulted in bug fixes to the graphics drivers.

In the case of the recently-filed Chrome issues, the WebGL team wasn't
made aware of the bugs until a few days ago. We would appreciate help
reducing the shaders into test cases, and will gladly accept pull
requests to the conformance suite acting as regression tests. This
will also help identify what shader constructs are causing the poor

It is impossible for the browser to detect all shader compilation and
execution problems ahead of time, but where it can, we will try to.

Finally, apologies for the slow reply; I fell behind on email some
weeks ago and didn't fully catch up.


On Mon, May 11, 2015 at 12:13 AM, Florian Bösch <pyalot@gmail.com> wrote:
> Tickets for this last one:
> Chrome: https://code.google.com/p/chromium/issues/detail?id=486636
> Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1163502
> Safari: https://bugs.webkit.org/show_bug.cgi?id=144859
> Let me know if you need more details or if you can reproduce it on your own.

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl