Open Bug 1768259 Opened 3 years ago Updated 2 years ago

Video playback stops near the beginning of a file and hitting play again doesn't work

Categories

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

defect

Tracking

()

Tracking Status
firefox-esr91 --- unaffected
firefox100 --- wontfix
firefox101 --- wontfix
firefox102 --- wontfix
firefox103 --- fix-optional

People

(Reporter: smaug, Assigned: alwu)

References

(Regression)

Details

(Keywords: regression)

Something odd happening with http://pettay.fi/summer2020.mp4
Often when opening that, only the very first seconds are played.
Reloading the whole page may help or dragging the slider to the beginning of the video.

Tried both Nightly and the FF version which comes with Fedora 35, and also Nightly on Windows 11.
Other browsers work fine.

Hmm, this is possibly a regression. Esr does pause for a second or two when it is loading more data, but eventually the video is played.

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

Oh, the behavior is really odd. Happened to leave the video open in a tab for a longer period, and looks like it does restart also in Nightly, but only after 10 seconds or so. Almost as if the full video needs to be somehow processed in the background.

Has Regression Range: --- → yes

The full video can be played on my Windows 10 and MacOS 12.2. As the video is H264, it's not related bug 1713276 because we only use ffmpeg on Linux for h264.

The longer period of wait seems related with the file itself. At least on Windows, I see the in the beginning, the decoder returned video frames to us very slowly. What would happen if you disable the pref media.ffmpeg.customized-buffer-allocation on Linux? Would the file play smoothly without any buffering?

Thanks.

Flags: needinfo?(alwu) → needinfo?(bugs)

media.ffmpeg.customized-buffer-allocation = false fixes the issue. First a bit is played, then more is buffered and the rest is then played immediately. If that pref it true, a bit is played, then more is buffered and then one needs to wait about 10 seconds and then playback continues.

I got the regression range using linux and I got the same result twice, even when starting from different good and bad builds.

Flags: needinfo?(bugs)

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)

I will take a look on this.

Assignee: nobody → alwu
Severity: -- → S3
Flags: needinfo?(jmathies)
Priority: -- → P3

:alwu was there any further investigation on this?

Flags: needinfo?(alwu)

No, this is still in my backlog and I probably won't be back to this soon recently because there are other higher priority tasks.

Flags: needinfo?(alwu)
You need to log in before you can comment on or make changes to this bug.