Bug 1820370 Comment 26 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

There seemed to be too many GPU-related tasks during the STR. Tasks during the STR could be roughly categorized like the followings.

- [1] Hardware video decoding
- [2] video frame copy
- [3] Sync object in RenderCompositorANGLE::BeginFrame()
- [4] GPU tasks of scrolling at WebRender
- [5] Video rendering GPU tasks at WebRender
- [6] Access GPU Query in RenderCompositorANGLE::GetLastCompletedFrameId() and in RenderCompositorANGLE::WaitForPreviousGraphicsCommandsFinishedQuery()
- [7] mDevice->GetDeviceRemovedReason() in RenderCompositorANGLE::IsContextLost()

[2] could be removed by zero video frame copy.
It seems that [3] could be reduced.
I am not sure [4] could be reduced.
There seemed to be too many GPU-related tasks during the STR. Tasks during the STR could be roughly categorized like the followings.

- [1] Hardware video decoding
- [2] video frame copy
- [3] Sync object in RenderCompositorANGLE::BeginFrame()
- [4] GPU tasks during scrolling at WebRender
- [5] Video rendering GPU tasks at WebRender
- [6] Access GPU Query in RenderCompositorANGLE::GetLastCompletedFrameId() and in RenderCompositorANGLE::WaitForPreviousGraphicsCommandsFinishedQuery()
- [7] mDevice->GetDeviceRemovedReason() in RenderCompositorANGLE::IsContextLost()

[2] could be removed by zero video frame copy.
It seems that [3] could be reduced.
I am not sure [4] could be reduced.
There seemed to be too many GPU-related tasks during the STR. Tasks during the STR could be roughly categorized like the followings.

- [1] Hardware video decoding
- [2] video frame copy
- [3] Sync object in RenderCompositorANGLE::BeginFrame()
- [4] GPU tasks during scrolling at WebRender
- [5] Video rendering GPU tasks at WebRender
- [6] Access GPU Query in RenderCompositorANGLE::GetLastCompletedFrameId() and in RenderCompositorANGLE::WaitForPreviousGraphicsCommandsFinishedQuery()
- [7] mDevice->GetDeviceRemovedReason() in RenderCompositorANGLE::IsContextLost()

[2] could be removed by zero video frame copy.
It seems that [3] could be reduced.
I am not sure if [4] could be reduced.

Back to Bug 1820370 Comment 26