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, though it may have been masked
by code changes since around the last time this was seen.
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Changed in: mir
Status: Triaged => Invalid
--
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=<optimized out>)
at /build/mir-
xon0uu/mir-0.14.1+15.04.20150821/src/server/scene/application_session.cpp:237
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1494062/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
