https://www.khronos.org/bugzilla/show_bug.cgi?id=870 describes a shader which
takes a very long time to compile, apparently only on Windows machines with
NVIDIA GPUs. I don't have a Windows machine with an AMD GPU to test with to see
if it only reproduces there:
https://www.shadertoy.com/view/MsX3WH
Chrome's infrastructure appears to be working as expected; the Chrome process
becomes unresponsive for a few seconds until the GPU process's watchdog fires,
and WebGL is disabled for the domain. The questions are (a) whether the failure
is NVIDIA-specific and (b) whether anything can be done to reduce the
compilation time. There aren't any loops in the shader, so time is probably
being spent in register allocation in Microsoft's shader compiler, or somewhere
similar.
Original issue reported on code.google.com by kbr@chromium.org on 20 May 2013 at 8:01
Original issue reported on code.google.com by
kbr@chromium.org
on 20 May 2013 at 8:01