Closed Bug 1546852 Opened 6 years ago Closed 5 years ago

Investigate to use SharedGL for copying SurfaceTexture for content process

Categories

(Core :: Graphics: WebRender, enhancement, P3)

Product:
Core
Component:
Graphics: WebRender
Platform:
Unspecified
Android
Type:
enhancement

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: sotaro, Assigned: sotaro)

References

(Blocks 1 open bug)

Details

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

OS: Unspecified → Android
Assignee: nobody → sotaro.ikeda.g
Depends on: 1544642
Blocks: wr-android
Type: defect → enhancement
Priority: -- → P3

It is better to replace the bug by Bug 1562818 .

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
See Also: → 1617051
You need to log in before you can comment on or make changes to this bug.