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é : 37.0.2062.
Candidat : 37.0.2062.
Table de version :
*** 37.0.2062.
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.
ProcVersionSign
Uname: Linux 3.16.0-12-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Sep 5 17:11:58 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-04-05 (152 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
ProcEnviron:
SHELL=/bin/bash
LD_LIBRARY_
PATH=(custom, no user)
LANG=fr_FR.UTF-8
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f3ab8910be8: movl $0x1337,0x0
PC (0x7f3ab8910be8) 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 audio cdrom dialout dip lpadmin plugdev sambashare sudo
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.