[Bug 100231] Freezing Linux machine by accessing site with WebGL shader

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Mar 16 13:57:13 UTC 2017


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

            Bug ID: 100231
           Summary: Freezing Linux machine by accessing site with WebGL
                    shader
           Product: Mesa
           Version: 13.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: al2510 at imperial.ac.uk
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 130259
  --> https://bugs.freedesktop.org/attachment.cgi?id=130259&action=edit
glxinfo output from affected machine

We have found a WebGL shader which, when rendered in Chrome, leads to
consistent browser hang, and sometimes to a complete system freeze (at which
point the machine is not even pingable). We were able to consistently replicate
the machine freeze via a script, which launches Chrome attempting to render the
shader successively. We were unable to reproduce the bug in Firefox (where we
observed the tab crashing every time, but no system issues), and reported it to
Chrome. After an analysis by the Chrome group, we were advised to report it
here.

The machine is running an Archlinux installation, with manually installed Mesa
13.0.3, with an Intel Core i7-2600. The reported renderer string is "Mesa DRI
Intel(R) Sandybridge Desktop". The full output of "glxinfo" is attached.

We have prepared a webpage which contains the source of the WebGL shader and
attempts to render it shortly upon being opened, as well as the script which
successively launches Chrome. Due to potential misuse, we are reluctant about
making the shader public. Should we upload the shader on this tracker, or is
there an alternative channel that we should be using?

-- 
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/intel-3d-bugs/attachments/20170316/6efc5124/attachment.html>


More information about the intel-3d-bugs mailing list