<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - dri3: chrome/chromium gpu acceleration (and therefore webgl) doesn't work"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=81706">81706</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>idr@freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>dri3: chrome/chromium gpu acceleration (and therefore webgl) doesn't work
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-3d-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>haagch@frickel.club
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>git
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Drivers/DRI/i965
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Mesa
          </td>
        </tr></table>
      <p>
        <div>
        <pre>In current stable you have to override the blacklist for it to enable gpu
acceleration anyway, so this is more of a feature request to investigate why
this happens with dri3 but not with dri2. For non-working webgl this is
probably a little bit more serious.

On current google-chrome-unstable on a fresh profile with default settings gpu
acceleration is enabled.
When it is manually enabled via chrome://flags and checking "Override software
rendering list", this has happened at least since one or two stable versions,
probably always.

Symptoms:

$ google-chrome-unstable
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: option value of option force_s3tc_enable ignored.
[20081:20081:0724/093124:ERROR:command_buffer_proxy_impl.cc(153)] Could not
send GpuCommandBufferMsg_Initialize.
[20081:20081:0724/093124:ERROR:webgraphicscontext3d_command_buffer_impl.cc(236)]
CommandBufferProxy::Initialize failed.
[20081:20081:0724/093124:ERROR:webgraphicscontext3d_command_buffer_impl.cc(256)]
Failed to initialize command buffer.

this is repeated two times and chrome://gpu has these Log Messages:

GpuProcessHostUIShim: The GPU process crashed!
GpuProcessHostUIShim: The GPU process crashed!
GpuProcessHostUIShim: The GPU process crashed!


But with LIBGL_DRI3_DISABLE=1 google-chrome-unstable it works without issues.

Ivy Bridge, xorg 1.16, xf86-video-intel with sna and mesa both from recent git.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>