[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix ** Changed in: unity8 (Ubuntu) Status: New => Won't Fix ** Changed in: canonical-devices-system-image Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** No longer affects: ubuntu-app-launch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1671731 Title: [xmir] closing an app while a child window is opened leaves

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Changed in: canonical-devices-system-image Status: Confirmed => Triaged ** Changed in: canonical-devices-system-image Milestone: u8c-1 => u8c-z -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu.

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

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

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1671731 Title: [xmir] closing an app while a

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

This is simple to reproduce. The application has disappeared from the screen but continues to run. It looks like qtmir is closing the window (as requested) but no word gets out to the actual process (ie. there is no session management). I'm suspecting the Unity 8 lifecycle for desktops is not in

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Changed in: canonical-devices-system-image Importance: Medium => High ** Changed in: canonical-devices-system-image Milestone: None => u8c-1 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Stephen M. Webb (bregma) ** Tags added: unity8-desktop -- You

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1671731 Title: [xmir] closing an app while a child

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

Sorry, wrong bug... ** No longer affects: xorg-server (Ubuntu) ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Tags added: xmir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to