Mir

android platform holds client compositor buffers when screen is off

Bug #1350961 reported by Alberto Aguirre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
High
Alberto Aguirre
0.6
Fix Released
High
Alberto Aguirre
Mir 0.6.0
mir (Ubuntu)
Fix Released
High
Unassigned

Bug Description

The Android platform holds unto client compositor buffers when the screen is off when the option "--disable-overlays=false" is set.

This prevents BufferQueue from advancing the compositor buffer during timeout framedrops so a very stale frame is shown after turning the screen back on.

Related branches

lp://staging/~albaguirre/mir/fix-1350961
PS Jenkins bot (community): Approve (continuous-integration)
Kevin DuBois (community): Approve
Diff: 83 lines (+30/-2)
5 files modified
src/platform/graphics/android/hwc_common_device.cpp (+6/-1)
src/platform/graphics/android/hwc_common_device.h (+2/-1)
src/platform/graphics/android/hwc_device.cpp (+5/-0)
src/platform/graphics/android/hwc_device.h (+1/-0)
tests/unit-tests/graphics/android/test_hwc_device.cpp (+16/-0)
lp://staging/ubuntu/utopic-proposed/mir
Alberto Aguirre (albaguirre)
Changed in mir:
assignee: nobody → Alberto Aguirre (albaguirre)
importance: Undecided → High
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: New → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Isn't this a duplicate of bug 1340510? Although if you look in that bug there's another cause we haven't fixed yet.

Changed in mir:
milestone: none → 0.7.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Manual merge into lp:mir/0.6 at r1815.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → High
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0 at a late stage. I've verified everything in 0.6.0 is also fixed in 0.7.0. So although the branched fixes in 0.7.0 have not been "released" yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7 any more.

Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.