chromium-browser crashed with SIGSEGV in base::debug::TaskAnnotator::RunTask()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i686 (athlon, cpu - a8-4500)
15.04
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: chromium-browser 41.0.2272.
ProcVersionSign
Uname: Linux 3.19.0-12-generic i686
NonfreeKernelMo
ApportVersion: 2.17-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Apr 5 15:41:22 2015
Desktop-Session:
'ubuntu'
'/etc/
'/usr/
DetectedPlugins:
Env:
'None'
'None'
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-12-15 (111 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141214)
Load-Avg-1min: 1.89
Load-Processes-
MachineType: LENOVO IdeaPad Z585
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb3f90107: movl $0x1337,0x0
PC (0xb3f90107) 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/
?? () from /usr/lib/
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
dmi.bios.date: 01/03/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 60CN17WW
dmi.board.
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: Lenovo LZ23BC
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: IdeaPad Z585
dmi.product.
dmi.sys.vendor: LENOVO
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 #1272693, 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.