Closed Bug 1937249 Opened 2 months ago Closed 2 months ago

Stutter and frame drops are observed while playing 8K@60Hz Youtube videos on Firefox

Categories

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

Firefox 135
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: paul.blinzer, Unassigned)

Details

Steps to reproduce:

GPU: Navi 31 XTX Retail
PC: Intel Raptorlake desktop system (Reference board)
Operating System: Windows SV2 (22621.1413)
Display Used: LG 27GP950-B via DisplayPort
Graphics Driver: Adrenalin 24.12.1
RAM: 32 GB

Install FireFox
Launch Youtube
Play any 8k video (ex. PATAGONIA 8k)
Set the clip to 4320p60 8k

Actual results:

frame drops and stutter when playing 8k 60 fps content

Expected results:

Smooth playback with no stutter and frame drop.

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

I've been going over Firefox profiles trying to identify the issue here and I'm not seeing it in the profiles but I can clearly see it in gpuview, so I'm going to see if I can find what these hw queue entries are that are causing it to back up every 4th vsync for a variable amount of time.

This seems to have been fixed in nightly from my testing, no longer seeing this texture copy on newly recorded profiles or in new recordings for gpuview. I don't know if it has been uplifted to Beta or Release or ESR releases, as there's been no update on this bug.

NeedInfo - Does this still repro on Firefox Nightly?

Flags: needinfo?(paul.blinzer)
Status: UNCONFIRMED → NEW
Ever confirmed: true

We have confirmed that this issue doesn't repro on the latest nightly build. Ticket can be closed. Thanks for investigating this and whatever change has been made shows up in the stable release soon.

Status: NEW → RESOLVED
Closed: 2 months ago
Flags: needinfo?(paul.blinzer)
Resolution: --- → WORKSFORME

This may have been caused by bug 1932772 (which is now disabled on Nightly)

You need to log in before you can comment on or make changes to this bug.