1588574 - in 1440p60 videos on Twitch, the video just randomly freezes

Status: RESOLVED FIXED

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

Description

[Dan]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Watch this video for some time in fullscreen on a 1920x1080 screen. (in 1440p60, since thats the only format in that video and in many other Twitch videos)
https://www.twitch.tv/videos/490722322?t=09m48s

Actual results:

After some time (maybe also with closing and opening fullscreen view) video will freeze, audio continue.

Expected results:

Video should keep playing.

Comment 1

[Peter Magyari (Desktop QA)]

Hi Daniel,

I was not able to reproduce this issue on Firefox 69.0.3 or Firefox Nightly 71.0a1.

Please try using a new profile and/or disable hardware acceleration in Firefox and see if the issue persists.

You can find the steps to make a new profile below:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Also, to disable hardware acceleration, go to about:preferences -> uncheck the "Use recommended performance settings" and then also uncheck the "Use hardware acceleration when available" options.

Thanks!

Comment 2

[Dan]

Yes, also occurs in 69.0.3 with new profile with HwAcc deactivated.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 4

[Dan]

Fixed in 72.0a1 with HW accelleration deactivated. However FF Beta still affected with new profile, regardless of HW accel. on/off. That's why I'm pushing this to P1 as there are over 150 other P2 audio/video-playback bugs currently (Of which some are quite old...).
Can we push this fix into Firefox Beta asap please, can one of you test for the regression with mozregression aswell? (Otherwise I could do this in the weekend maybe, don't have the time currently)

Comment 5

[Alex Chronopoulos [:achronop]]

Hi Daniel, thank you for your input and all the work that you have done so far. I believe this error does not justify for P1. This priority is for release blockers or other emergencies. I would suggest to keep it as P3 but if you want to give it emphasis at least change it to P2.

Regarding the error, I am not able to repro in beta. This type of problem often depends on specific hardware set up. However, if we find out what fixed it in Nightly I will be happy to uplift it in beta (if it is upliftable). Thank you.

Comment 6

[Peter Magyari (Desktop QA)]

Hi Daniel,

Since I cannot reproduce the issue, I won't be able to find what fixed it in Nightly either I'm afraid.

Comment 7

[Dan]

but isn't the "Severity" for that? That's why I kept it at "normal" Severity. Yes, I'm very curious what mozregression will find when I get to it this weekend.

Comment 8

[Dan]

Ran mozregression (9 tries...), it resulted in identifying mozilla-central build 7a3378ad as the version where it was fixed in. mozilla-central build 7f0c7ef8 is still the faulty one apparently.

How do we now proceed to get that change uplifted to FF Beta asap? :)

Comment 9

[Alex Chronopoulos [:achronop]]

According to the comment above Bug 1576697 has fixed this error in Nightly. Does it make sense to you? Is Bug 1576697 upliftable in beta?

Comment 10

[Toshihito Kikuchi [:toshi]]

Bug 1576697 has nothing to do with video rendering. I don't think it's related to this issue.

Comment 11

[Dan]

related to this then?
https://hg.mozilla.org/mozilla-central/log?rev=7a3378ad

Which would be one of these?
https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=7a3378adb34084d5d19352d45abbaa1bee681ac8

Comment 12

[Toshihito Kikuchi [:toshi]]

(In reply to Daniel from comment #11)

related to this then?
https://hg.mozilla.org/mozilla-central/log?rev=7a3378ad

7a3378ad is for Bug 1576697.

Which would be one of these?
https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=7a3378adb34084d5d19352d45abbaa1bee681ac8

If this list is correct, Bug 1579028 looks related a little bit, but I'm not sure.

Comment 13

[Dan]

And despite all the crash-logs that Mozilla receives on crash-stats.mozilla.com since 3 months, the bugfix STILL didn't get uplifted to Beta/release? Why not?

Comment 14

[John Lin [:jhlin][:jolin]]

This bug has been fixed since FF 72 according to comments above. Since the release version of FF is 73 now. I am closing this bug for now. If it still happens, please reopen it.