← Back to team overview

desktop-packages team mailing list archive

[Bug 1385570] [NEW] chromium-browser crashed with SIGSEGV in gpu::gles2::GLES2DecoderImpl::Initialize()

 

*** This bug is a duplicate of bug 1378627 ***
    https://bugs.launchpad.net/bugs/1378627

Public bug reported:

chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 on Lubuntu Utopic amd64
sometimes crashes on launch. This happens at least daily, but somewhat
less than half the time the browser is launched. Following the crash and
without deliberately relaunching the application, Chromium usually still
seems to work (but Chromium uses multiple processes, so that is not
surprising). This is on a laptop with Intel i915 onboard video.

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
       capabilities: pm msi vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:109 memory:d0000000-d03fffff memory:c0000000-cfffffff ioport:f080(size=8)

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
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/chromium-browser/chromium-browser
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=16578.0.637767605\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0f31\ --gpu-driver-vendor\ --gpu-driver-versi
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::GLES2DecoderImpl::Initialize()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-10-18T02:01:31.797924

** Affects: chromium-browser (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1385570

Title:
  chromium-browser crashed with SIGSEGV in
  gpu::gles2::GLES2DecoderImpl::Initialize()

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 on Lubuntu Utopic amd64
  sometimes crashes on launch. This happens at least daily, but somewhat
  less than half the time the browser is launched. Following the crash
  and without deliberately relaunching the application, Chromium usually
  still seems to work (but Chromium uses multiple processes, so that is
  not surprising). This is on a laptop with Intel i915 onboard video.

  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
         capabilities: pm msi vga_controller bus_master cap_list rom
         configuration: driver=i915 latency=0
         resources: irq:109 memory:d0000000-d03fffff memory:c0000000-cfffffff ioport:f080(size=8)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  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/chromium-browser/chromium-browser
  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=16578.0.637767605\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0f31\ --gpu-driver-vendor\ --gpu-driver-versi
  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::GLES2DecoderImpl::Initialize()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-10-18T02:01:31.797924

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1385570/+subscriptions


Follow ups

References