1914908 - YouTube stuck at loading "log_event" URL

Status: RESOLVED INVALID

(Core :: Networking, defect)

Description

[Selim Şumlu]

I'm mirroring this issue from the support forum.

The user has been experiencing problems with youtube.com pages since upgrading to Firefox 128.0.3. The homepage loads very slowly and video pages keep loading forever.

Here's the profile he recorded: https://share.firefox.dev/4dLLtBo

He can reproduce this on troubleshooting mode and he doesn't have any security software, VPN or proxy installed.

Initially I thought it could be bug 1910820 but apparently it's not.

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

Can he try this after logging out of youtube/google? 'log_event' is something internal to youtube; the server doesn't appear to be responding.
I assume "the homepage" means Youtube's homepage?
Taking a network log via about:logging could confirm that it's the server.
The only other thing I can think of to do would be to reboot his router (I assume that doesn't have any VPN setup and doesn't have any other sort of blocking enabled), or try disabling http3 or http2 via about:config (though I seriously doubt those will change anything).

Comment 2

[Selim Şumlu]

(In reply to Randell Jesup [:jesup] (needinfo me) from comment #1)

Can he try this after logging out of youtube/google? 'log_event' is something internal to youtube; the server doesn't appear to be responding.

He couldn't log out because not even the YouTube menu loads properly.

I assume "the homepage" means Youtube's homepage?

Yes.

Taking a network log via about:logging could confirm that it's the server.
The only other thing I can think of to do would be to reboot his router (I assume that doesn't have any VPN setup and doesn't have any other sort of blocking enabled), or try disabling http3 or http2 via about:config (though I seriously doubt those will change anything).

I've also asked him try these but none of them helped as you suspected.

Comment 3

[Valentin Gosu [:valentin] (he/him)]

Hi Selim,

Can you ask the reporter for another profile?
They should load about:logging?output=profiler&preset=networking, start logging, then reproduce, stop logging, then upload the profile.

Thanks!

Comment 4

[Selim Şumlu]

Here it is: https://share.firefox.dev/4cMHW4R

I should also mention that he can't reproduce this on any non-Firefox browser.

I've asked him try it on a fresh installation of Nightly and he can reproduce it on Nightly.

Comment 5

[Valentin Gosu [:valentin] (he/him)]

From what I can tell, there's a redirect loop happening there in mozilla::net::nsHttpChannel::ContinueOnBeforeConnect.

{
  "start": 98347.7525,
  "data": {
    "type": "Log",
    "module": "nsHttp",
    "name": "nsHttpChannel::ContinueOnBeforeConnect [this=1550b190c00 aShouldUpgrade=0 rv=0]\n"
  }
}

Since we don't do HTTPS upgrades if aShouldUpgrade is false, It seems this is a RedirectToInterceptedChannel case.

Selim, could you ask the reporter if setting dom.serviceWorkers.enabled to false in about:config fixes the bug?

Thanks!

Comment 6

[Selim Şumlu]

(In reply to Valentin Gosu [:valentin] (he/him) from comment #5)

Selim, could you ask the reporter if setting dom.serviceWorkers.enabled to false in about:config fixes the bug?

He says it didn't have any affect.

Comment 7

[Valentin Gosu [:valentin] (he/him)]

Could you have the reporter capture one final log with: about:logging?output=profiler&preset=networking&profilerstacks.
They should make sure to have dom.serviceWorkers.enabled set to false.

Thanks!

Comment 8

[Selim Şumlu]

Here it is: https://share.firefox.dev/3Mpzfmb

Comment 9

[Kershaw Chang [:kershaw]]

(In reply to Selim Şumlu from comment #8)

Here it is: https://share.firefox.dev/3Mpzfmb

This profile shows that a proxy is used. Could you ask the reporter to test without proxy and see if they can still reproduce?
If yes, could you also ask the reporter to capture a log file with this about:logging?output=file&preset=networking?

Thanks.

Comment 10

[Selim Şumlu]

You're right. He had a proxy configured in Windows settings which was the source of the problem, and Firefox was configured to use system proxy settings.

I've specifically asked him if he has any proxy or VPN configured before filing this bug, but apparently he forgot about it.

Apologies for taking your time.

Comment 11

[Valentin Gosu [:valentin] (he/him)]

Thank you for your help.