Crash when closing second app

Bug #1220845 reported by Gerry Boland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
High
Robert Carr
unity-mir
Fix Released
High
Unassigned
unity-mir (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Quoting Daniel d'Andrada

I can launch and close a single app at a time, no problem.
But if I launch a second one (having therefore two apps running simultaneously) I get a crash when switching between them (with right edge gesture) or trying to close one of them (through the dash thumbnail).

Got this stacktrace:

#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#1 0x40b195fe in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0x40b1be1a in __GI_abort () at abort.c:90
#3 0x40a937ac in __gnu_cxx::__verbose_terminate_handler () at
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#4 0x40a921cc in __cxxabiv1::__terminate (handler=<optimized out>) at
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:38
#5 0x40a91676 in __cxa_call_terminate (ue_header=0x1074f60) at
../../../../src/libstdc++-v3/libsupc++/eh_call.cc:54
#6 0x40a91f06 in __cxxabiv1::__gxx_personality_v0 (state=<optimized
out>, ue_header=0x1074f60, context=<optimized out>)
    at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:670
#7 0x401747d6 in unwind_phase2 (ucbp=ucbp@entry=0x1074f60,
vrs=vrs@entry=0x4fddaa24) at ../../../src/libgcc/unwind-arm-common.inc:294
#8 0x401749a6 in __gnu_Unwind_Resume (ucbp=0x1074f60,
entry_vrs=0x4fddaa24) at ../../../src/libgcc/unwind-arm-common.inc:502
#9 0x401751ae in _Unwind_Resume () at
../../../src/libgcc/config/arm/libunwind.S:344
#10 0x41076bd2 in mir::frontend::SessionMediator::~SessionMediator() ()
from /usr/lib/arm-linux-gnueabihf/libmirserver.so.1
#11 0x40bd3000 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Cannot access memory at address 0x2
#12 0x40bd3000 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Cannot access memory at address 0x2

Related branches

Gerry Boland (gerboland)
Changed in unity-mir:
importance: Undecided → Critical
importance: Critical → High
status: New → Confirmed
Changed in mir:
assignee: nobody → Robert Carr (robertcarr)
importance: Undecided → High
Changed in mir:
status: New → In Progress
Revision history for this message
Robert Carr (robertcarr) wrote :

It's hard to understand how the crash as I have seen it (And am unable to reproduce it with linked branch) could lead to this stacktrace. Maybe some mir changes moved it.

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:unity-mir at revision 90, scheduled for release in unity-mir, milestone Unknown

Changed in unity-mir:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-mir - 0.1+13.10.20130926.2-0ubuntu1

---------------
unity-mir (0.1+13.10.20130926.2-0ubuntu1) saucy; urgency=low

  [ Gerry Boland ]
  * Adding controller for Display power mode and a DBus API to allow
    other processes to adjust it.

  [ Robert Carr ]
  * Check default surface before snapshotting preventing a crash. (LP:
    #1220845)

  [ Kevin Gunn ]
  * [deb] bump mir{client,server} dependence to 0.0.12

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 92
 -- Ubuntu daily release <email address hidden> Thu, 26 Sep 2013 11:47:04 +0000

Changed in unity-mir (Ubuntu):
status: New → Fix Released
kevin gunn (kgunn72)
Changed in unity-mir:
status: Fix Committed → Fix Released
Changed in mir:
status: In Progress → Fix Released
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.