I was given this link: http://hunger.hu/webgl.html which was supposed to crash any video driver, and it really did a hiccup. Fortunately, after 1 second the kernel detected GPU lockup, and reinitialized everything just fine. As far as I can tell that javascript doesn't do anything sinister, just tries to render 200k triangles with a single glDrawElements() call. Shouldn't there be a protection against such simple overflows somewhere?
It can be impossible to tell the difference between a draw that will take a very long time and a draw that will never complete, so possibly not. See also http://en.wikipedia.org/wiki/Halting_problem.
Did you set your lockup timeout to 1s? I recommend reverting to the default timeout (10s).
(In reply to Ian Romanick from comment #1) > It can be impossible to tell the difference between a draw that will take a > very long time and a draw that will never complete, so possibly not. See > also http://en.wikipedia.org/wiki/Halting_problem. That's why WebGL was a bad idea in the first place. As far as I can remember the timeout was 1 second, but since then I upgraded my system, kernel included, and when I tried now the timeout was 10s.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/537.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.