Crash when closing second app
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/
#1 0x40b195fe in __GI_raise (sig=sig@entry=6) at
../nptl/
#2 0x40b1be1a in __GI_abort () at abort.c:90
#3 0x40a937ac in __gnu_cxx:
../../.
#4 0x40a921cc in __cxxabiv1:
../../.
#5 0x40a91676 in __cxa_call_
../../.
#6 0x40a91f06 in __cxxabiv1:
out>, ue_header=
at ../../.
#7 0x401747d6 in unwind_phase2 (ucbp=ucbp@
vrs=vrs@
#8 0x401749a6 in __gnu_Unwind_Resume (ucbp=0x1074f60,
entry_vrs=
#9 0x401751ae in _Unwind_Resume () at
../../.
#10 0x41076bd2 in mir::frontend:
from /usr/lib/
#11 0x40bd3000 in ?? () from /lib/arm-
Cannot access memory at address 0x2
#12 0x40bd3000 in ?? () from /lib/arm-
Cannot access memory at address 0x2
Related branches
- Daniel van Vugt: Needs Fixing
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Alan Griffiths: Abstain
- Alexandros Frantzis (community): Needs Information
-
Diff: 288 lines (+44/-14)5 files modifiedinclude/server/mir/shell/application_session.h (+1/-1)
include/server/mir/shell/surface.h (+3/-0)
src/server/shell/application_session.cpp (+0/-10)
src/server/shell/surface.cpp (+40/-1)
tests/unit-tests/shell/test_application_session.cpp (+0/-2)
- Gerry Boland (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/modules/Unity/Application/applicationscreenshotprovider.cpp (+1/-1)
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 |
Changed in unity-mir: | |
status: | Fix Committed → Fix Released |
Changed in mir: | |
status: | In Progress → Fix Released |
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.