<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Freezing Linux machine by accessing site with WebGL shader"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100231">100231</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Freezing Linux machine by accessing site with WebGL shader
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>13.0
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>al2510@imperial.ac.uk
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=130259" name="attach_130259" title="glxinfo output from affected machine">attachment 130259</a> <a href="attachment.cgi?id=130259&action=edit" title="glxinfo output from affected machine">[details]</a></span>
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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>