I spent a little time on this bug last week. Was able to reproduce it, yes, but the spinning thread was apparently the libmirclient input thread, and not in any Xmir code. I didn't have sufficient libmirclient symbols to debug it further before running out of time. I had assumed this was an Xmir bug but it looks like it might actually be a Mir bug.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671731 Title: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671731/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
