diff options
author | lionel.g.landwerlin <lionel.g.landwerlin@intel.com> | 2015-04-16 04:48:31 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-04-16 11:48:46 +0000 |
commit | ee1b10bd38de9e6f96e491bd30c63577e22a9bae (patch) | |
tree | 03d4611c6b5c1634b0d562ea05199facf68a64de /extensions/renderer/guest_view | |
parent | 7b45a34b0d0da16f07829b471d01d878ac170da2 (diff) | |
download | chromium_src-ee1b10bd38de9e6f96e491bd30c63577e22a9bae.zip chromium_src-ee1b10bd38de9e6f96e491bd30c63577e22a9bae.tar.gz chromium_src-ee1b10bd38de9e6f96e491bd30c63577e22a9bae.tar.bz2 |
cc: VideoResourceUpdater: don't dismiss the sync_point given by the compositor
When the compositor is done using a video texture, it returns a
sync_point associated with the last use of this texture. We appear to
drop this sync_point on the floor, neither waiting on it, nor
associating it to the video frame returned to the GpuVideoDecoder.
This change emits a WaitSyncPointCHROMIUM on the compositor sync point
when updating the renderer's media::VideoFrame release sync point.
BUG=chrome-os-partner:37786
Review URL: https://codereview.chromium.org/1088903002
Cr-Commit-Position: refs/heads/master@{#325416}
Diffstat (limited to 'extensions/renderer/guest_view')
0 files changed, 0 insertions, 0 deletions