touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

This bug does not exist in Mir 0.7, because the fix was released in the
0.6 series before 0.7 branched from it. However a separate fix exists in
development-branch so it's still not "Fix Released" for 0.8 just yet.

** Changed in: mir
    Milestone: 0.7.0 => 0.8.0

** Also affects: mir/0.7
   Importance: Undecided
       Status: New

** Changed in: mir/0.7
       Status: New => Invalid

-- 
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/1352883

Title:
  nexus 4 client lock up observed

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Fix Released
Status in Mir 0.7 series:
  Invalid
Status in “mir” package in Ubuntu:
  Fix Released

Bug description:
  I was playing with the demo shell extensively working on a branch and
  observed a client drop to 10 self-reported fps for about 1s and then
  jump back to 60fps. What was probably happening was a fence was
  getting stuck, eventually timing out, and continuing on. The fps drop
  was probably just the framedropping algorithm kicking in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1352883/+subscriptions