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

Re: [Public WebGL] shader compilation hangs/crashes

This is something we hope the community can contribute to.

I think when Ken mentioned about minimized test cases, he meant not
just the entire crashing shadertoy shader (which is usually pretty
big), but a reduced shader that's rid of all unnecessary code, so it's
clearer if there is a pattern, then we can detect the pattern in
shader translator, either  fail the compile or rewrite (work around)
some patterns to make the compile successful.

On Wed, May 13, 2015 at 10:04 AM, Florian Bösch <pyalot@gmail.com> wrote:
> On Wed, May 13, 2015 at 6:06 PM, Vladimir Vukicevic <vladimir@mozilla.com>
> wrote:
>> 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.
> That's why I called for massive testing of shaders, which are fortunately
> found aplenty on shadertoy and glslsandbox. There really isn't a good reason
> to have unidentified/unhandled/unworked-around driver bugs manifest itself
> when the browser exercises the driver when there's test material easily
> available.

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