Silly me. Mir seems to be behaving correctly, although I can think of some improvements. The real issue here is that dynamic double buffering relies on the compositor (over)scheduling enough frames for the performance detection to work. That means calling: mir::compositor::Scene::frames_pending() and compositing that many frames as a _minimum_. We just haven't added support for the algorithm fully to qtmir's compositor code yet.
** Also affects: qtmir Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir Importance: Undecided => High ** Changed in: qtmir (Ubuntu) Importance: Undecided => High ** Summary changed: - Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters + Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476201 Title: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1476201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs