chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
(((
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 34.0.1847.
ProcVersionSign
Uname: Linux 3.16.0-4-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Jul 21 21:55:31 2014
Desktop-Session:
DESKTOP_SESSION = ubuntu
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
DetectedPlugins:
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-05-01 (81 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7f816e489b88: movl $0x1337,0x0
PC (0x7f816e489b88) 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/
base::
base::
base::
?? () from /usr/lib/
Title: chromium-browser crashed with SIGSEGV in base::MessageLo
UpgradeStatus: Upgraded to utopic on 2014-07-12 (8 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
gconf-keys: /desktop/
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 #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.