ARC++: Transparent surfaces are composited by Chrome |
||||||||||||||
Issue descriptionLooks like a regression since switching to cc::surfaces. We're now compositing one fullscreen transparent buffer above everything when ARC++ is enabled. This has a major performance impact on low bandwidth devices.
,
Aug 25 2016
,
Aug 25 2016
,
Aug 25 2016
This change only effects ChromeOS devices with ARC++ and provides a critical performance improvement on those devices.
,
Aug 25 2016
[Automated comment] Less than 2 weeks to go before stable on M53, manual review required.
,
Aug 30 2016
,
Aug 30 2016
Approving merge to M53 cros.
,
Aug 30 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8b50ca09664b21db2a2abb04d76199daf347b3bd commit 8b50ca09664b21db2a2abb04d76199daf347b3bd Author: David Reveman <reveman@chromium.org> Date: Tue Aug 30 20:59:59 2016 exo: Avoid creating transparent texture quads. The surface is fully transparent when alpha is 0 and we can then avoid to create a texture quad completely. Failing to do so currently results in unnecessary compositing. BUG= 640805 TEST=exo_unittests Review-Url: https://codereview.chromium.org/2277833004 Cr-Commit-Position: refs/heads/master@{#414220} (cherry picked from commit e2d54b85fbc32bd0d19e1741677a296e25fd47c7) Review URL: https://codereview.chromium.org/2293223002 . Cr-Commit-Position: refs/branch-heads/2785@{#794} Cr-Branched-From: 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382} [modify] https://crrev.com/8b50ca09664b21db2a2abb04d76199daf347b3bd/components/exo/surface.cc
,
Aug 30 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Aug 25 2016