chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Had the browser on http://
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.
ProcVersionSign
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Jul 30 21:15:57 2014
Desktop-Session:
DESKTOP_SESSION = None
XDG_CONFIG_DIRS = None
XDG_DATA_DIRS = None
DetectedPlugins:
DiskUsage:
b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 158G 94G 56G 63% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/
Inodes:
b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 10M 317K 9.7M 4% /\nnone 922K 2 922K 1% /sys/fs/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-06-21 (42 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7f88725a5b88: movl $0x1337,0x0
PC (0x7f88725a5b88) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
gconf-keys: /desktop/
modified.
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.