Mir

unity-system-compositor crashed with SIGSEGV in ~task_cleanup

Bug #1216329 reported by Jaime Rave
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Incomplete
Medium
Unassigned
Unity System Compositor
Invalid
Medium
Unassigned
mir (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I was opening synaptic and compiz crashed and after that this error appear.

The compiz crash was reported as bug 1216325

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-system-compositor 0.0.1+13.10.20130822.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Sat Aug 24 09:33:50 2013
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5730 / 6570M] [1002:68c0] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1594]
InstallationDate: Installed on 2013-03-16 (161 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f41b4733f74 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f41b4733f74) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-system-compositor
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x14af1f0) at pthread_mutex_lock.c:50
 boost::asio::detail::task_io_service::run(boost::system::error_code&) () from /usr/lib/x86_64-linux-gnu/libmirserver.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 start_thread (arg=0x7f41a6759700) at pthread_create.c:311
Title: unity-system-compositor crashed with SIGSEGV in __GI___pthread_mutex_lock()
UnitySystemCompositorLog:
 dm_connection_start
 set_active_session '0'
 set_active_session
 Segmentation fault (core dumped)
UpgradeStatus: Upgraded to saucy on 2013-03-17 (160 days ago)
UserGroups:

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

Revision history for this message
Jaime Rave (jaimerave) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x14af1f0) at pthread_mutex_lock.c:50
 lock (this=<optimized out>) at /usr/include/boost/asio/detail/posix_mutex.hpp:52
 lock (this=0x14af220) at /usr/include/boost/asio/detail/scoped_lock.hpp:52
 ~task_cleanup (this=0x7f41a6758d30, __in_chrg=<optimized out>) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:48
 do_run_one (ec=..., this_thread=..., lock=..., this=<optimized out>) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:396

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
Jaime Rave (jaimerave)
description: updated
affects: unity-system-compositor (Ubuntu) → unity-system-compositor
information type: Private → Public
summary: - unity-system-compositor crashed with SIGSEGV in
- __GI___pthread_mutex_lock()
+ unity-system-compositor crashed with SIGSEGV in ~task_cleanup
kevin gunn (kgunn72)
Changed in mir:
status: New → Invalid
Changed in unity-system-compositor:
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The crash seems to be entirely in libmirserver.

Changed in mir:
status: Invalid → Triaged
importance: Undecided → Medium
Changed in unity-system-compositor:
status: Triaged → Invalid
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

I doubt this is relevant now

Changed in mir:
status: Triaged → Incomplete
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mir (Ubuntu) because there has been no activity for 60 days.]

Changed in mir (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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