Closed Bug 1757971 Opened 2 years ago Closed 2 years ago

Video is frozen after seeking on youtube.com

Categories

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

Product:
Core
Component:
Audio/Video: Playback
Version:
Firefox 99
Platform:
Unspecified
Linux
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
100 Branch
Project Flags:
Webcompat Priority P1
Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox97 --- unaffected
firefox98 --- unaffected
firefox99 + fixed
firefox100 + fixed

People

(Reporter: ksenia, Assigned: jbauman)

References

(Regression,
URL
)

Details

(Keywords: regression)

We've received 2 reports about a problem on youtube.com after seeking a video on a Linux machine in Firefox Nightly 99.0.

https://github.com/webcompat/web-bugs/issues/99842:

When I'm watching a video and pressing the back arrow key to move back in the video, only audio is heard, video is stuck and randomly and different points, generally around where i pressed the back arrow, works perfectly again. Reversing the video with the bottom red line works, only not the back arrow. Where only audio comes and video is stuck on a single frame, sometimes 2 until it's perfect again.

https://github.com/webcompat/web-bugs/issues/100351:

Video is often frozen after seeking.
Keep seeking around by clicking on the time line and video will eventually freeze. Sometimes it recovers after seeking again.
This only seems to affect files using AV1 ("Codecs" in "Stats for nerds" starts with "av01").
Chrome functions properly.
My system does not support hardware decoding of AV1.

Example of a video: https://www.youtube.com/watch?v=D66n31vUeyI

One of the reporters was able to bisect it and it points to 1754070

Last good revision: ff5d9e91a332cf67e670ffc60668904eb541e2d5
First bad revision: 65e07dc89d820de46bbdcdc769fa517a66803f10
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ff5d9e91a332cf67e670ffc60668904eb541e2d5&tochange=65e07dc89d820de46bbdcdc769fa517a66803f10

Regressed by https://bugzilla.mozilla.org/show_bug.cgi?id=1754070

Hi Tom, wonder if you could take a look at this?

Flags: needinfo?(tom)

Passing to owner

Flags: needinfo?(tom) → needinfo?(jbauman)

[Tracking Requested - why for this release]: This is affecting youtube.com on Linux.

tracking-firefox99: --- → ?
Webcompat Priority: --- → P1

Set release status flags based on info from the regressing bug 1754070

status-firefox97: --- → unaffected
status-firefox98: --- → unaffected
status-firefox-esr91: --- → unaffected
Has Regression Range: --- → yes
Blocks: media-triage
See Also: → 1756914

Can this ticket be assigned for investigation?

Flags: needinfo?(jmathies)

I wonder if the issue could be fixed by the next update in bug 1758482?

Just chatted with the dav1d developers and have confirmed it's a known issue. Will follow up here with more details when I confirm the specifics of the fix and whether it's included in bug 1758482 or whether I'll do another update manually to grab it.

Flags: needinfo?(jbauman)
Assignee: nobody → jbauman

Set release status flags based on info from the regressing bug 1754070

status-firefox100: --- → affected
Flags: needinfo?(jmathies)
Severity: -- → S1
tracking-firefox100: --- → ?
Priority: -- → P1

Is this limited to Linux, or could we see the same issue on other platforms that are using dav1d?

No longer blocks: media-triage

Per the dav1d team, the fix is across 3 commits:

None of the code there looks platform-specific to me, thought there may be other reasons why it only shows up on Linux. I can inquire with the dav1d devs if the answer is important. Either way, it should be fixed shortly.

(In reply to Jon Bauman [:jbauman:] from comment #12)

Per the dav1d team, the fix is across 3 commits:

None of the code there looks platform-specific to me, thought there may be other reasons why it only shows up on Linux. I can inquire with the dav1d devs if the answer is important. Either way, it should be fixed shortly.

Thanks! I ask so we can rule out if non-linux bugs are this or not. My assumption was folks on other platforms can have this issue, so if people are having problems like this it may make sense to wait and see if the patches helps. If the fix is landing shortly, that works for me. We can chase further on any bugs if they're not resolved following landing.

(In reply to Jon Bauman [:jbauman:] from comment #12)

Per the dav1d team, the fix is across 3 commits:

These appear to be dupes. Copy / paste error?

Yes, good catch. Fixed now.

Depends on: 1758482

:jbauman - Is the dav1d update something we are going to be able to land and uplift onto the 99 branch?

Flags: needinfo?(jbauman)

(In reply to James Graham [:jgraham] from comment #16)

:jbauman - Is the dav1d update something we are going to be able to land and uplift onto the 99 branch?

And ultimately going to be the 1.0.0 final (https://code.videolan.org/videolan/dav1d/-/milestones/20)?

Yup! I just landed the update yesterday, so I wanted to make sure it didn't hit any snags, but I'm going to request uplift shortly.

This is fixed by the dav1d update in bug 1758482, and uplift has been requested for Fx99 beta

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(jbauman)
Resolution: --- → FIXED
status-firefox100: affected → fixed
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.