chromium-browser crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Chromium Browser |
Unknown
|
Unknown
|
|||
Mesa |
Won't Fix
|
Medium
|
|||
chromium-browser (Debian) |
Fix Released
|
Unknown
|
|||
chromium-browser (Fedora) |
Won't Fix
|
Undecided
|
|||
chromium-browser (Ubuntu) |
Fix Released
|
Medium
|
Chad Miller |
Bug Description
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.
ProcVersionSign
Uname: Linux 3.16.0-21-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Oct 8 07:12:48 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-12-22 (289 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7fc0e6b1963f: mov 0x1f8(%rax),%r15
PC (0x7fc0e6b1963f) ok
source "0x1f8(%rax)" (0x000001f8) not located in a known VMA region (needed readable region)!
destination "%r15" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
modified.
mtime.conffile.
tags: | added: bugpattern-needed |
Changed in chromium-browser (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
Changed in chromium-browser (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in chromium-browser (Debian): | |
status: | Unknown → Confirmed |
Changed in mesa: | |
importance: | Unknown → Medium |
status: | Unknown → Invalid |
Changed in mesa: | |
importance: | Unknown → Medium |
status: | Unknown → Won't Fix |
Changed in chromium-browser (Debian): | |
status: | Confirmed → Fix Released |
Changed in chromium-browser (Fedora): | |
importance: | Unknown → Undecided |
status: | Unknown → Won't Fix |
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 20081:0724/ 093124: ERROR:command_ buffer_ proxy_impl. cc(153) ] Could not send GpuCommandBuffe rMsg_Initialize . 20081:0724/ 093124: ERROR:webgraphi cscontext3d_ command_ buffer_ impl.cc( 236)] CommandBufferPr oxy::Initialize failed. 20081:0724/ 093124: ERROR:webgraphi cscontext3d_ command_ buffer_ impl.cc( 256)] Failed to initialize command buffer.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: option value of option force_s3tc_enable ignored.
[20081:
[20081:
[20081:
this is repeated two times and chrome://gpu has these Log Messages:
GpuProcessHostU IShim: The GPU process crashed! IShim: The GPU process crashed! IShim: The GPU process crashed!
GpuProcessHostU
GpuProcessHostU
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.