Open Bug 1566732 Opened 1 year ago Updated 7 months ago

[arm64] Some videos and live streams get stuck after switching to 1080 resolution


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

Windows 10



Tracking Status
firefox68 --- affected
firefox69 --- affected
firefox70 --- affected
firefox71 --- affected
firefox72 --- affected
firefox73 --- affected
firefox74 --- affected


(Reporter: tbabos, Unassigned, NeedInfo)


(Blocks 1 open bug)


(Whiteboard: [media-performance])

Affected versions:
Nightly aarch64 70.0a1
Beta aarch64 v69.0b5
Release aarch64 v68.0

Affected platforms:
ARM64 - Windows 10

Steps to reproduce:

  • Launch Firefox
  • Go to any live streaming platform, such as twitch or youtube
  • View any live stream that has 1080p resolution in settings
  • Switch to 1080 resolution

Expected Firefox:

  • The live streams should update the resolution and be played back without any issues.

Actual Result:

  • The video will get stuck at a frame while the audio is still on-going.

Switching the resolution to a lower scale will fix this.
On Chrome live streams and videos work properly with 1080 resolution or higher
Normal videos can also stutter if higher resolutions are selected than the native one.

Here is an example of a normal video with 1080p 60fps that is constantly getting stuck frames and audio on-going:

Summary: [arm64] Live stream videos get stuck after switching to 1080 resolution → [arm64] Some videos and live streams get stuck after switching to 1080 resolution

Nils, any thoughts on who should take a look at this? I marked it P2 for now.

Flags: needinfo?(drno)
Priority: -- → P2

Reproducible on latest Nightly 73 on the same devices, marking the other version affected as well.

Reproducible on latest Nightly 74 on the same ARM YOGA laptop.

This is h.264 being decoded in software on these machines, could it be that this bit rate is simply too much for these low-powered machines to keep up?

Priority: P2 → P3
Whiteboard: [media-performance]
You need to log in before you can comment on or make changes to this bug.