1758528 - YouTube slow, freezing and stutter video.

Status: RESOLVED FIXED

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

Description

[ESV]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0

Steps to reproduce:

Since 2-3 months ago, I have been suffering continuously YouTube problems (slow reproduction, freezing and stutter). I'm not sure but It seems Firefox 95 was working well and 96 and 97 brought the problem.

Actual results:

After made some research I found in Reddit a suggestion to disable the TCP/IPv6, I did that and verified it works, no more problems watching YouTube videos, they are running very smooth right know. Please, take care on this issue because it is annoying, there was a time I thought to switch to a different browser after more than 10 years using Firefox. Regards.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Alastor Wu [:alwu]]

Hi,
Would you mind to capture profiles for enabling and disabling TCP/IPv6, which might help us find what the differences are between this two situations.
Thank you.

Comment 3

[ESV]

Hi,
I can't open the profiler, I'm receiving a message "The profiler is currently disabled, most likely due to a private browsing window being opened ", I tried using Firefox in normal mode but it still disabled, not sure how proceed further.
Regards.

Comment 4

[Jim Mathies [:jimm]]

Could you please post your about:support text?

Comment 5

[Jim Mathies [:jimm]]

Also, could you test to see if you actually have ipc v6 available via this page?

https://ipv6-test.com/

Comment 6

[ESV]

(In reply to Jim Mathies [:jimm] from comment #5)

Also, could you test to see if you actually have ipc v6 available via this page?

https://ipv6-test.com/

Results when IPv6 is enabled on PC:

IPv4 connectivity
IPv4 Supported
Address 177.248.223.46
Hostname 177.248.223.46-clientes-zap-izzi.mx
ISP Cablevision Red, S.A de C.V. [Mexico]
IPv6 connectivity
IPv6 Supported
Address 2806:310:102:887b:f943:78a1:963b:65f1
Type Native IPv6
SLAAC No
ICMP Not tested
Hostname None
Score
15 / 20

Default IPv4
Fallback to IPv6 in 1 second
DNS
DNS4 + IP6 Reachable
DNS6 + IP4 Reachable
DNS6 + IP6 Unreachable

Results when IPv6 is disabled on PC:

IPv4 connectivity
IPv4 Supported
Address 177.248.223.46
Hostname 177.248.223.46-clientes-zap-izzi.mx
ISP Cablevision Red, S.A de C.V. [Mexico]
IPv6 connectivity
IPv6 Not supported
Address
Type
SLAAC
ICMP
Hostname
ISP
Browser
Score
4 / 20

Default IPv4
Fallback No
DNS
DNS4 + IP6 Unreachable
DNS6 + IP4 Reachable
DNS6 + IP6 Unreachable

Comment 7

[Alastor Wu [:alwu]]

(In reply to ESV from comment #3)

Hi,
I can't open the profiler, I'm receiving a message "The profiler is currently disabled, most likely due to a private browsing window being opened ", I tried using Firefox in normal mode but it still disabled, not sure how proceed further.
Regards.

It could be there is still another Firefox instance running on another desktop, on Windows it's kinda confusing. Could you try to restart your computer and see if the profiler can run on your Firefox or not?

Also, would you mind to post your about:support as well?

Thank you so much.

Comment 8

[Julien Wajsberg [:julienw]]

Also, the latest version of Firefox (v98) released 2 days ago should be able to profile even if private windows are opened.

Comment 9

[ESV]

Hi All,
After update to Firefox 98 as per Julien's' recommendation, it seems the problem has gone. I tested using IPv4 and IPv6 (alone and together) getting almost the same performance. I feel my equipment is now working as it used to do. I suppose Firefox 96 & 97 were demanding more resources from the cpu and memory causing the video interruptions and stutter.
Thanks for your support.

Comment 10

[Alastor Wu [:alwu]]

Per comment 9, this issue has been fixed by updating to Fx98, close this bug.

Comment 11

[Jeff Muizelaar [:jrmuizel]]

ESV, would you be willing to use mozregression to try to find the change that fixed the problem for you in 98?