Closed Bug 1414418 Opened 7 years ago Closed 2 years ago

Frame Dropping in videos and very high GPU usage

Categories

(Core :: Audio/Video: Playback, defect, P3)

58 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: kadencombs, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Steps to reproduce:

I went to a video on YouTube and I noticed major video lag/ frame dropping.


Actual results:

Major frame dropping and very high GPU usage found in task manager. YouTube said FireFox dropped about 6000 frames out of 15000( 6000/15000 frames dropped) (About 40%)


Expected results:

I compared it to the other browser that I use (Brave) and I played the same video and Brave played the video way smoother and used way less GPU usage. Youtube said that the video dropped about 6000 frames in Firefox and only dropped about 900 frames in Brave. Here is the comparison. https://gyazo.com/2416f8de65e416de0de81bc9ec70b390
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
Severity: normal → major
OS: Unspecified → Windows 10
In the video comparison Brave is on the left and Firefox is on the right.
Any chance of running mozregression tool and finding out when this started?
Flags: needinfo?(kadencombs)
My guess, this is a duplicate of bug 1414596
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(kadencombs)
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Will this get fixed?
It has been, and this is why this was made a duplicate.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → DUPLICATE
The same thing is still happening for me.
You need to make sure you're running the latest nightly.
Provide also a copy of about:config


Your comparison with brave is irrelevant really. It's getting h264 content, while Firefox is getting vp9 jere
H264 is hardware accelerated while obviously your machine doesn't have VP9 hardware decoding capabilither and so is software decoded. It will cause much higher CPU usage (but use less bandwidth and provide better video quality)


You'll probably find the same type of CPU usage with Chrome, as it too will be getting vp9 from YouTube.

If you want it to behave like Brave, then disable vp9 by using an extension like h264ify or disabling media.webm.enabled (set it to false)
(In reply to kadencombs from comment #1)
> In the video comparison Brave is on the left and Firefox is on the right.
It looks like the left (on my left side) used VP9 and the right used avc1. 
Are you sure Firefox is on the right?
(In reply to Blake Wu [:bwu][:blakewu] from comment #9)
> (In reply to kadencombs from comment #1)
> > In the video comparison Brave is on the left and Firefox is on the right.
> It looks like the left (on my left side) used VP9 and the right used avc1. 
> Are you sure Firefox is on the right?

Yeah, Firefox Nightly is on the right.
Status: RESOLVED → REOPENED
Ever confirmed: true
Priority: -- → P2
Resolution: DUPLICATE → ---
I just updated Firefox Nightly and now it's a little better on most videos but now it completely freezes on 1080p60 video.
Can you go to your URL bar to enter about:support and paste the content here?

I played the video on latest Nightly 96.0a1 (Win 10 x64), 4k quality and only had around 20 frames dropped.
@kadencombs, in case you're using the same system, could you please retest in latest Nightly and return with the results? Thank You!

Flags: needinfo?(kadencombs)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:jimm, since the bug has high priority and high severity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(kadencombs) → needinfo?(jmathies)
Flags: needinfo?(jmathies)
Priority: P2 → P3

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

This should work well these days, we've performed a lot of optimizations for those codecs, please comment or reopen if you're still seeing issues.

Status: REOPENED → RESOLVED
Closed: 7 years ago2 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.