86436ef01e
Before this CL VideoDecoderResource and VideoDecoderShim (via PepperVideoDecoderHost) would exchange textures using legacy mailbox system. With this CL we replace it with SharedImages. Old flow: * Renderer sends RequestTextures() * Plugin allocates textures, puts them in a legacy mailbox and sends back AssignTextures. * Renderer will pick a free texture, copy video frame into it and send texture id with PictureReady. * After plugin used texture and don't need it anymore it sends texture back with RecyclePicture. * When renderer doesn't need textures anymore it sends DismissPicture. New flow: * Renderer allocates SharedImages whenever it needs them * Renderer picks free SI, copy video frame into it and sends mailbox with SharedImageReady. * Plugin gets texture id from it using CreateAndTexStorageSharedImage * After plugin is done with the texture, it deletes it (this deletes only plugin view of the texture, SharedImage still exists) and sends mailbox back. * When renderer doesn't need SI anymore it either Destroys it right away or waits for plugin to return it first. Change-Id: I1500de3a2254acf013ef715349df2e2ecb191322 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4741796 Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Pilar Molina Lopez <pmolinalopez@chromium.org> Reviewed-by: Derek Schuff <dschuff@chromium.org> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204238}
v8
@ 3eb7d73cbd
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.