chromium-browser crashed with SIGSEGV in gpu::gles2::GLES2DecoderImpl::Initialize()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
chromium-browser 37.0.2062.
When I launch Chromium, both in cases when a crash occurs and in cases when there is no crash, the Chromium window remains undrawn for a while (perhaps half a minute), showing whatever was last drawn behind it. This is confusing because it looks like other windows or the desktop are in the foreground and could be interacted with, when actually they are not--however, that is not the bug I am reporting here. Rather, I mention it in case it is related to the crash (since it looks like the crash may be related to OpenGL rendering).
In case it's relevant, the output of "sudo lshw -C video" is:
*-display
description: VGA compatible controller
product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 0e
width: 32 bits
clock: 33MHz
resources: irq:109 memory:
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.
ProcVersionSign
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXDE
Date: Fri Oct 24 23:22:44 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-10-15 (9 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141014)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7fea04d4c63f: mov 0x1f8(%rax),%r15
PC (0x7fea04d4c63f) 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
Title: chromium-browser crashed with SIGSEGV in gpu::gles2:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1378627, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.