chromium-browser crashed with SIGSEGV in base::debug::TaskAnnotator::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I frequently find this crash after leaving the computer on and logged in for serveral hours after unlocking the screen. The browser is still open and functional so I don't quite know what is crashing.
$ lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
$ apt-cache policy chromium-browser
chromium-browser:
Installed: 39.0.2171.
Candidate: 39.0.2171.
Version table:
*** 39.0.2171.
500 http://
500 http://
100 /var/lib/
34.
500 http://
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 39.0.2171.
ProcVersionSign
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 26 12:46:57 2015
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-07-18 (192 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7f1b2e5c1428: movl $0x1337,0x0
PC (0x7f1b2e5c1428) 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::
base::
Title: chromium-browser crashed with SIGSEGV in base::debug:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1402523, 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.