chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
gilles@
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
gilles@
chromium-browser:
Installé : 36.0.1985.
Candidat : 36.0.1985.
Table de version :
*** 36.0.1985.
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 36.0.1985.
ProcVersionSign
Uname: Linux 3.16.0-11-generic x86_64
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Sep 1 06:53:51 2014
Desktop-Session:
DESKTOP_SESSION = gnome
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-04-05 (148 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
ProcEnviron:
LD_LIBRARY_
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6e39329458: movl $0x1337,0x0
PC (0x7f6e39329458) 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 dialout dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/
modified.
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.