Google Chrome crash with mesa 10.3 on Intel GPU

[Laurent Bonnaud]

When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering.

In chrome://gpu/ I get:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Unavailable
Rasterization: Software only, hardware acceleration unavailable
Threaded Rasterization: Unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable

Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_ext_occlusion_query
disable_post_sub_buffers_for_onscreen_surfaces
scalarize_vec_and_mat_constructor_args

Problems Detected
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
[...]

In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libgl1-mesa-dri 10.3.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
  * Setting sensors limits 
[ OK ]
  * Setting up X socket directories... 
[ OK ]
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: kwin
CurrentDesktop: KDE
Date: Fri Oct 3 17:48:09 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: kubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0494]
MachineType: Dell Inc. Latitude E6520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Thu Oct 2 13:54:36 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 8685
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bartek Feltman (bfeltman)]

Confirmed.
After update to Beta 1 14.10 laptop loses GPU rendering in Chrome (tested stable and unstable). I have rev 07 GPU (GM45/Core 2 Duo)
It worked fine on 14.04. Tested on Unity and Gnome 3.14.

Settings chrome://flags/#ignore-gpu-blacklist doesn't help.

[Hyungchul Kim (blueball81)]

According to chromium forum, (https://code.google.com/p/chromium/issues/detail?id=418858)
this is related to the bugs of MESA 10 with the DRI3 feature.

If you disable the DRI3 feature when you run google-chrome as in the following, GPU works.

# LIBGL_DRI3_DISABLE=1 google-chrome

I confirmed with Ubuntu 14.10 beta and google-chrome 38.

[Laurent Bonnaud (laurent-bonnaud)]

Good catch, thanks !
I confirm that this workaround also works on my system.

[Laurent Bonnaud (laurent-bonnaud)]

Should we reassign this bug to chrome/chromium ?

[Anna Glasgall (aglasgall)]

This also affects Haswell and I assume Ivy Bridge. I confirm that the LIBGL_DRI3_DISABLE workaround fixes the issue for me on Haswell.

[Raman Monorath (ramanmono)]

I confirm this bug also affects Ivy Bridge. But though the "LIBGL_DRI3_DISABLE" work around does enable gpu, it introduces other graphical freezes when going in full screen mode, tested in YouTube html5 player. It makes the whole graphical session unresponsive.

[Raman Monorath (ramanmono)]

When starting chrome(ium) with --disable-gpu-sandbox option, GPU acceleration works properly.

[Haw Loeung (hloeung)]

I've been running with --disable-gpu-sandbox since the 14th and so far haven't experienced any more issues with crashes and lock ups.

[Dzmitry_Hancharou (pretenderr)]

The same problem

[bademux (bademux)]

fast'n'dirty patch
sudo sed -i's/Exec=chromium-browser/Exec=env LIBGL_DRI3_DISABLE=1 chromium-browser/g' /usr/share/applications/chromium-browser.desktop
It is possible you have to apply the patch to
~/.local/share/applications/chromium-browser.desktop

[Anders Kaseorg (andersk)]

Chrome 40 now sets LIBGL_DRI3_DISABLE=1 automatically on desktop Linux (https://code.google.com/p/chromium/issues/detail?id=415681).

[Pauli (paniemin)]

Issue might be actually the X driver and mesa disagreeing how to handle the memory buffers.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435

[Pi Delport (pi-delport)]

This affects me too: Acceleration and WebGL worked fine in Ubuntu 14.04, and broke after upgrading to 14.10.

I use Google Chrome (google-chrome-stable 39.0.2171.99-1), also with an Intel integrated GPU (Lenovo G580 laptop), and Mesa 10.3.0.

The LIBGL_DRI3_DISABLE=1 workaround works for me: i applied it in ~/.local/share/applications/google-chrome.desktop, and WebGL functionality seems to be restored.

I haven't run it like this for very long, but it seems stable so far.

[Raman Monorath (ramanmono)]

With Chrome 40, the problem isn't properly fixed for me. HW acceleration does work, but the display/graphic session still crashes in full screen (tested with youtube html5 player), especially when you use a compiz animation (I often use the scale plugin).

[makis (sapouric)]

Had same problems with Intel GPU and Ubuntu 14.10.Problem seems to be fixed by updating kernel to 3.19 rc7.

[Hua Zhang (zhhuabj)]

I hit the same problem, LIBGL_DRI3_DISABLE=1 workaround doesn't work for me , but kernel 4.0.0-999-generic ( http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ ) can fix my problem as makis said.

[Timo Aaltonen (tjaalton)]

should be fixed by now