webapp-container crashed with SIGSEGV in QSGDefaultRenderer::renderNodes()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webbrowser-app (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Segfault appeard on mail.google.com
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: webapp-container 0.23+14.
ProcVersionSign
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 11 09:26:32 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-01-15 (26 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: webapp-container --app-id=
SegvAnalysis:
Segfault happened at: 0x7f520a213901: mov 0x10(%rdi),%r10
PC (0x7f520a213901) ok
source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%r10" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webbrowser-app
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
QSGDefaultRend
Title: webapp-container crashed with SIGSEGV in QSGDefaultRende
UpgradeStatus: Upgraded to trusty on 2014-02-10 (0 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
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 #1277793, 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.