| commit | 0a3a2b534686549ca30cece7f17598181bda5e6d | [log] [tgz] |
|---|---|---|
| author | Marissa Wall <marissaw@google.com> | Fri Feb 22 10:50:32 2019 -0800 |
| committer | Marissa Wall <marissaw@google.com> | Fri Feb 22 10:50:32 2019 -0800 |
| tree | 7e298e0e32b1e4828ef284a35d5ef591af82e607 | |
| parent | b2069ebab1de906ed02383dcd6467f3eb184b53e [diff] |
blast: adding a buffer doesn't make the frame dirty
The frame shouldn't be marked as dirty when a new buffer is set.
When a frame is marked as dirty, it forces SurfaceFlinger to do
extra work on the CPU which hurts power/performance.
Bug: 125859110
Test: Take a systrace when running the Blast Chrome.apk. Check that
there is no extra work done.
Change-Id: I0cf9802f495a7e9f2e5b1f4e58f0a7a4a75d8225