** Changed in: mir
Milestone: 0.19.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Crash in mir::scene::ApplicationSession::name (this=)
at /build/mir-
xon0uu/mir-0.14
** Changed in: mir
Milestone: 0.18.0 => 0.19.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Crash in mir::scene::ApplicationSession::name (this=)
at /build/mir-
xon0uu/mir-0.
This bug hasn't been encountered for about 2 months. Looking at the
stack trace, it seems to me that qtmir is accessing 'name' member of a
session that's already been destroyed, from the
onSessionDestroyingSurface function. I don't think this is a problem in
Mir, but may still be a problem in qtmir
** Changed in: mir
Milestone: 0.17.0 => 0.18.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Crash in mir::scene::ApplicationSession::name (this=)
at /build/mir-
xon0uu/mir-0.
** Changed in: mir
Milestone: 0.16.0 => 0.17.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Crash in mir::scene::ApplicationSession::name (this=)
at /build/mir-
xon0uu/mir-0.
Or we're perhaps trying to get the name of an ApplicationSession object
that no longer exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Crash in mir::scene::ApplicationSession::n
Whoops. It's not a reference. But still might be due to some std::string
optimization (COW) ?...
std::string const session_name;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494062
Title:
Cra
