[Bug 81706] New: dri3: chrome/chromium gpu acceleration (and therefore webgl) doesn't work

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jul 24 00:51:43 PDT 2014


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

          Priority: medium
            Bug ID: 81706
          Assignee: idr at freedesktop.org
           Summary: dri3: chrome/chromium gpu acceleration (and therefore
                    webgl) doesn't work
        QA Contact: intel-3d-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: haagch at frickel.club
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/i965
           Product: Mesa

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20140724/c28f80c2/attachment.html>


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