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

Re: [Public WebGL] shader compilation hangs/crashes



Thanks Florian, I've moved them to the Core - WebGL component and made our team aware of them.

I can understand if a shader fails to compile. I can understand if a shader, once compiled will run incredibly slow. What I cannot understand is that simply compiling a shader should hang/crash the software attempting to compile it.

These aren't shader compilation hangs/crashes, though; bug 1163502 is crashing in DrawArrays() inside the GL driver, and bug 1154688 is crashing somewhere in nvidia-land, not clear from where (that one might be a compilation issue, will need actual debugging to figure out where).

So we need to identify what situation is causing the crashes and avoid it on these particular drivers (assuming it's not a general issue).  If they were pure compilation crashes, we could do something like do a trial compilation run in a separate process and make sure it doesn't crash; but that's not the case unfortunately.

    - Vlad


On Mon, May 11, 2015 at 3: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.