chromium-browser crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
this happens every time chromium starts. presumably it's a duplicate
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 39.0.2171.
ProcVersionSign
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Jan 7 15:52:00 2015
ExecutablePath: /usr/lib/
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=
SegvAnalysis:
Segfault happened at: 0x7fb9d0a9463f: mov 0x1f8(%rax),%r15
PC (0x7fb9d0a9463f) ok
source "0x1f8(%rax)" (0x000001f8) not located in a known VMA region (needed readable region)!
destination "%r15" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: Upgraded to utopic on 2014-12-30 (8 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data
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 #1378627, 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.