Bug 1544642 is going to address SurfaceTexture video rendering to WebGL by excluded use of SurfaceTexture based on guessing. It is not ideal. On android with WebRender, there is already SharedGL on render thread. It is ideal if we could use SharedGL for copying SurfaceTexture for content process. But SharedGL exists on render thread. It could add latency to content side. The following diagram shows how video's SurfaceTexture is consumed in content process. https://github.com/sotaroikeda/firefox-diagrams/blob/master/mobile/mobile_SurfaceAllocatorService_68.pdf
Bug 1546852 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Bug 1544642 is going to address SurfaceTexture video rendering to WebGL by excluded use of SurfaceTexture based on guessing. It is not ideal. On android with WebRender, there is already SharedGL on render thread. It is ideal if we could use SharedGL for copying SurfaceTexture for content process, since we do not need the excluded access. But SharedGL exists on render thread. It could add latency to content side. The following diagram shows how video's SurfaceTexture is consumed in content process. https://github.com/sotaroikeda/firefox-diagrams/blob/master/mobile/mobile_SurfaceAllocatorService_68.pdf
Bug 1544642 is going to address SurfaceTexture video rendering to WebGL by exclusive use of SurfaceTexture based on guessing. It is not ideal. On android with WebRender, there is already SharedGL on render thread. It is ideal if we could use SharedGL for copying SurfaceTexture for content process, since we do not need the exclusive access. But SharedGL exists on render thread. It could add latency to content side. The following diagram shows how video's SurfaceTexture is consumed in content process. https://github.com/sotaroikeda/firefox-diagrams/blob/master/mobile/mobile_SurfaceAllocatorService_68.pdf