chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

[Matthias Andree]

I'm not sure when exactly this happened - the browser is still up

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 26 07:57:32 2014
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=13711.0.1660615688\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x9614\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x7f0fd23c6d98: movl $0x1337,0x0
 PC (0x7f0fd23c6d98) ok
 source "$0x1337" ok
 destination "0x0" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from /usr/lib/chromium-browser/libs/libbase.so
 ?? () from /usr/lib/chromium-browser/libs/libbase.so
Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
UpgradeStatus: Upgraded to trusty on 2014-08-29 (27 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-08-30T00:07:57.340239

[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 #1229021, 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.