Mir

unity-system-compositor crashed with SIGSEGV in std::_Hashtable<std::shared_ptr<mir::input::Device>, std::shared_ptr<mir::input::Device>, std::allocator<std::shared_ptr<mir::input::Device> >, std::__detail::_Identity, std::equal_to<std::shared_ptr<mir::input::Device> >, std::hash<std::shared_ptr<mir::input::Device> >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, true, true> >::~_Hashtable()

Bug #1560382 reported by bogz
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mir
Won't Fix
High
Unassigned
Unity System Compositor
Won't Fix
High
Unassigned
unity-system-compositor (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Ubuntu 16.04 on a VmWare vm, using VMware-tools-linux-10.0.5

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Wed Mar 16 13:16:44 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-02-17 (33 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
ProcCmdline: /usr/sbin/unity-system-compositor --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f0d1cacd471: mov 0x10(%rax),%rax
 PC (0x7f0d1cacd471) ok
 source "0x10(%rax)" (0x7f0d0f616a70) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-system-compositor
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
 ?? ()
 std::_Hashtable<std::shared_ptr<mir::input::Device>, std::shared_ptr<mir::input::Device>, std::allocator<std::shared_ptr<mir::input::Device> >, std::__detail::_Identity, std::equal_to<std::shared_ptr<mir::input::Device> >, std::hash<std::shared_ptr<mir::input::Device> >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, true, true> >::~_Hashtable() ()
 usc::MirInputConfiguration::~MirInputConfiguration() ()
 std::_Sp_counted_ptr_inplace<usc::UnityInputService, std::allocator<usc::UnityInputService>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
Title: unity-system-compositor crashed with SIGSEGV in std::_Hashtable<std::shared_ptr<mir::input::Device>, std::shared_ptr<mir::input::Device>, std::allocator<std::shared_ptr<mir::input::Device> >, std::__detail::_Identity, std::equal_to<std::shared_ptr<mir::input::Device> >, std::hash<std::shared_ptr<mir::input::Device> >, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, true, true> >::~_Hashtable()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.17.6-0ubuntu1
version.mesa: libegl1-mesa-dev N/A

Revision history for this message
bogz (orbai) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _M_release (this=0x7f0cf800d6e0) at /usr/include/c++/5/bits/shared_ptr_base.h:150
 ~__shared_count (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/c++/5/bits/shared_ptr_base.h:659
 ~__shared_ptr (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/c++/5/bits/shared_ptr_base.h:925
 ~shared_ptr (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/c++/5/bits/shared_ptr.h:93
 mir::input::DefaultDevice::~DefaultDevice (this=<optimized out>, __in_chrg=<optimized out>) at /build/mir-ZgPdOQ/mir-0.20.2+16.04.20160307/src/server/input/default_device.h:43

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-system-compositor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Changed in mir:
importance: Undecided → High
Changed in unity-system-compositor:
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-system-compositor (Ubuntu):
status: New → Confirmed
Changed in mir:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
Changed in unity-system-compositor:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
Changed in mir:
status: New → Confirmed
Changed in unity-system-compositor:
status: New → Confirmed
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

AFAIK we've not seen these crashes on zesty which includes more recent versions of the associated projects. We're also not trying to support USC on xenial.

Changed in mir:
assignee: Andreas Pokorny (andreas-pokorny) → nobody
Changed in unity-system-compositor:
assignee: Andreas Pokorny (andreas-pokorny) → nobody
Changed in mir:
status: Confirmed → Won't Fix
Changed in unity-system-compositor:
status: Confirmed → Won't Fix
Changed in unity-system-compositor (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.