chromium-browser crashed with SIGSEGV

[Colan Schwartz]

Seems to crash often when clicking on a link in Thunderbird, instead of simply opening a new tab with the URL.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 38.0.2125.111-0ubuntu0.14.10.1.1103
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Nov 17 10:52:21 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=7754.0.1966674849\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0d26\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x7ff22ae3d63f: mov 0x1f8(%rax),%r15
 PC (0x7ff22ae3d63f) 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/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/chromium-browser/libs/libgpu.so
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to utopic on 2014-11-11 (6 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare staff sudo whoopsie
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-11-11T11:41:37.189973

[Apport retracing service (apport)]

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.