I know it looks confusing, but 0.23 and 0.24 get separate bug tasks here
because they got different fixes for this bug. The fix landed on 0.24
series after we had branched 0.23. So the two fixes have different
histories and need to be tracked separately.
** Changed in: mir
Milestone: None => 0.24.0
** Also affects: mir/0.23
Importance: Undecided
Status: New
** Changed in: mir/0.23
Status: New => Fix Released
** Changed in: mir
Status: Fix Released => Fix Committed
** Changed in: mir/0.23
Importance: Undecided => Critical
** Changed in: mir/0.23
Assignee: (unassigned) => Kevin Dubois (kevin-dubois05)
** Changed in: mir/0.23
Milestone: None => 0.23.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1578159
Title:
Performance loss with NBS and overlays on
Status in Mir:
Fix Committed
Status in Mir 0.23 series:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
If you run a server with overlays enabled on android devices with a
client, sporadically, the performance will dip between 1/2 vsync rate
and vsync rate. The dip is dependent on load, (it seems loads that tax
the system at near-vsync rates seem to cause the problem).
Should be fixed before 0.23 is published, so tagging as critical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1578159/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
