[Mesa-dev] [Bug 105755] Mesa freezes when the GLSL shader contains a `for` loop with an uninitialized `i` index/counter variable

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 28 00:47:24 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=105755

--- Comment #14 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Swyter from comment #12)
> detecting when the draw call/batch/job is idle spinning/stuck by having some
> kind of reasonable timeout and killing it with a descriptive message when
> things go out of hand, instead of making the entire system unusable. And
> this is where I'm probably talking about stuff I don't know about, but this
> could be probably enforced in the DRI/DRM side of things instead of being
> driver-specific.

Each driver is a separate implementation of DRM. Each driver has a separate
compiler. An infinite loop can happen without any warnings whatsoever (i.e.
done on purpose), and drivers ought to handle it gracefully.

But they don't. Killing jobs isn't always straightforward, GPU resets are a
plain disaster. This has to be done very much in concert with the hardware, so
each driver is on its own. I don't think any handle this well, but nouveau is
probably particularly bad.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180328/c39d1e3a/attachment.html>


More information about the mesa-dev mailing list