chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
apport-reported crash
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 32.0.1700.
ProcVersionSign
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Mon Mar 17 13:35:07 2014
Desktop-Session:
DESKTOP_SESSION = xubuntu
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
DiskUsage:
b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda5 ext4 386G 79G 288G 22% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/
Inodes:
b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda5 25M 861K 24M 4% /\nnone 983K 2 983K 1% /sys/fs/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-03-11 (370 days ago)
InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7f7ae2eeab98: movl $0x1337,0x0
PC (0x7f7ae2eeab98) 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 trusty on 2014-03-05 (12 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/
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.