unity8 crashed with SIGSEGV in memcpy() from mir::frontend::SessionMediator::request_persistent_surface_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
High
|
Unassigned | ||
Mir |
Won't Fix
|
High
|
Unassigned | ||
mir (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
unity8 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
unity8 crashed with SIGSEGV in memcpy()
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity8 8.14+16.
ProcVersionSign
Uname: Linux 4.8.0-19-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 1 16:15:40 2016
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2016-06-05 (117 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: unity8 --mode=full-shell
SegvAnalysis:
Segfault happened at: 0x7ff9d530a877 <memcpy+23>: movups (%rsi),%xmm0
PC (0x7ff9d530a877) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm0" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
memcpy () at ../sysdeps/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: unity8 crashed with SIGSEGV in memcpy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
summary: |
- unity8 crashed with SIGSEGV in memcpy() + unity8 crashed with SIGSEGV in memcpy() from + mir::frontend::SessionMediator::request_persistent_surface_id |
Changed in mir: | |
importance: | Undecided → High |
Changed in mir (Ubuntu): | |
importance: | Undecided → High |
tags: | added: unity8-desktop |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
Changed in mir: | |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
Changed in mir: | |
status: | Confirmed → Won't Fix |
Changed in mir (Ubuntu): | |
status: | Confirmed → Won't Fix |
Status changed to 'Confirmed' because the bug affects multiple users.