The resizing case is just the easiest manual test case for the mir demos. I'm not sure resizing is involved at all when we see the same jumping during unity8 touch usage on Nexus 10.
Also, even if Unity8 was resizing more than it needs to, Mir will ignore duplicate resize requests at multiple levels. So the original bug would have nothing to do with resizing or buffer allocation. Because buffers won't get reallocated during Unity8 touch usage. Unless there's some non-obvious behaviour in Unity8 I haven't considered... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: frame jumps on the nexus 10 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
