diff options
author | mmocny@chromium.org <mmocny@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-15 16:54:50 +0000 |
---|---|---|
committer | mmocny@chromium.org <mmocny@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-15 16:54:50 +0000 |
commit | 57f2d412a609adafa29cd7f041ab5306a9986a04 (patch) | |
tree | f4063b8be628c71a54f04ab16eef55d86b3797ff /media/mp4/cenc.cc | |
parent | 92bd85a11c851b6fb0bfdfe976e298d42543d554 (diff) | |
download | chromium_src-57f2d412a609adafa29cd7f041ab5306a9986a04.zip chromium_src-57f2d412a609adafa29cd7f041ab5306a9986a04.tar.gz chromium_src-57f2d412a609adafa29cd7f041ab5306a9986a04.tar.bz2 |
Drop frontbuffers with ui-use-gpu-process, synchronized with browser, decoupled from backbuffer drop.
On Aura, every time a tab is backgrounded, RenderWidgetHostViewAura will reset its handle to the front surface. If that tab is foregrounded again, that front surface will not be used until synchronizing with the gpu process to make sure that surface is still available. By doing this, the gpu process knows when it is safe to discard the front surface.
RWHVA sends a FrontSurfaceIsProtected(bool, int) message to the gpu process to keep it informed about front surface protection. The int is a state-of-the-world identifier to protect from ABA issues. RWHVA delays sending FrontSurfaceIsProtected(false) until after the current surface is certain to not be in use, namely after the compositor finishes the current frame and the browser thumbnailer is complete.
BUG=112842
TEST=Manual
Review URL: https://chromiumcodereview.appspot.com/10052018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142408 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/mp4/cenc.cc')
0 files changed, 0 insertions, 0 deletions