YouTube video quality changes from 1080p to lower quality randomly
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
People
(Reporter: groovin, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.53 Safari/537.36 Edg/103.0.1264.37
Steps to reproduce:
1 - Open YouTube
2 - Open any video
3 - Change the video quality to 1080p60
4 - Scroll through the video randomly (or pause before scrolling through video)
5 - Repeat the steps until the issue occurs
Actual results:
The video quality changes from 1080p60 to 720p.
Note that this issue happens even with fresh / new profile.
PC Specs (I reproduced on 2 different PC's)
CPU: i7 3770 / Ryzen 5800x3d
RAM: 8gb / 16gb
GPU: GT 1030 / 3060ti
OS: Windows 10 / Windows 11 (latest updates)
Firefox profiler after the issue happened:
https://share.firefox.dev/3zBLZRC
Expected results:
The video quality should remain the same.
|
||
Comment 1•3 years ago
|
||
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.
|
||
Comment 2•3 years ago
|
||
We have a profile here of youtube downgrading bandwidth served. Might be interesting to triage with the team.
|
||
Comment 3•3 years ago
•
|
||
By doing a quick check, I didn't find anything suspicious in this profile yet. The decoding time is fast enough in average for 60fps video by checking the markers (via extension), and the ratio of dropped frames is very little, which shouldn't make Youtube think that the user's computer is not strong enough.
Youtube started adding a new buffer for lower resolution video at ~65.3s, which was triggered by an event handler. But I checked the dom event around that range, I didn't find media element sending any suspicious event, just some normal ones (eg. timeupdate)
|
|
||
Comment 4•3 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
|
|
||
Updated•3 years ago
|
Hello. I can still reproduce the issue on v.103.0.2.
Same steps as in the original post.
Description
•