forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GpuMemoryBufferVideoFramePool: Split shared image binding from copying
Creating a frame using GpuMemoryBufferVideoFramePool has the following steps: A1. Create GpuMemoryBuffers (in FrameResources) on the media thread A2. Copy into those GpuMemoryBuffers on a worker thread A3. Create SharedImages for the GpuMemoryBuffers and wrap them in a VideoFrame on the media thread For the canvas capture path, the sequence of events will be B1. Create GpuMemoryBuffers B2. Create SharedImages and wrap them in a VideoFrame B3. Blit the source into those SharedImages Towards enabling the new path, take the function that does A3 or B2, BindAndCreateMailboxesHardwareFrameResources, and make it no longer depend on the copy that is done in A2 (or even the existence of a source video frame). Bug: 1207111 Change-Id: If9b73e710e9b9dd7ee848d0ca6e9442d90a17ff7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2942207 Reviewed-by: Dan Sanders <sandersd@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#891260}
- Loading branch information
1 parent
9477af3
commit 9f2b58b
Showing
1 changed file
with
63 additions
and
33 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters