New issue
Advanced search Search tips

Issue 787841 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Participants' hotlists:
Modern-Media-Controls


Sign in to add a comment

Video renders at 30FPS after animations end with new Media Controls

Project Member Reported by fbeaufort@chromium.org, Nov 22 2017

Issue description

Chrome Version       : 64.0.3274.0
OS Version: 10150.0.0

What steps will reproduce the problem?
1. Enable New Media Controls flag
2. Go to https://storage.googleapis.com/fbeaufort-test/sample-video.webm
3. Open DevTools / Performance panel
4. Start profiling and reload page with Ctrl+Shift+E
5. Wait for profile

What is the expected result?
All frames should be about 60FPS as there's only a video playing

What happens instead of that?
After animations end, frames are at 30FPS.

I've attached profile you can load in DevTools to understand what is happening.
 
Screenshot 2017-11-22 at 4.26.56 PM.png
586 KB View Download
Profile-20171122T162658.json
11.6 MB View Download
Owner: beccahughes@chromium.org
Status: Assigned (was: Unconfirmed)
I can reproduce on 65.0.3293.0
Cc: steimel@chromium.org
Owner: ----
Status: Available (was: Assigned)
I seem to be able to reproduce with the legacy controls as well. Are we sure this is connected to the new controls?
You're right Tommy, it is not connected to new controls. I can also reproduce with legacy controls.

I think* I've found what is happening...
https://storage.googleapis.com/fbeaufort-test/sample-video.webm is a 24fps video. I wonder if DevTools simply use that when there's nothing else needed to be updated at 60fps.

With another video file (this one at 60 fps), I can observe that the Perf timeline indicates 60fps consistently before and after video animations.

Is that intended?
Out of curiosity, what happens if you turn on the "Enable the use of SurfaceLayer objects for videos" flag?
Interesting, there are no more FPS available in DevTools. See screenshot attached. Is that intended?
Screenshot 2018-02-09 at 9.23.02 PM.png
196 KB View Download
Status: WontFix (was: Available)
That's what I was hoping to hear actually :) The new backend should no longer require repainting the entire page at the video framerate. It might make sense to open a bug on the devtools if you think the video actual fps should be visible there somehow but this seems to be WAI.

Sign in to add a comment