1913272 - Sometimes some pages (https://codepen.io/Dillo/pen/gONXJzz) did not open in Nightly while Chrome can open them

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Mayank Bansal]

Browsing as usual on my daily profile
Suddenly a URL (https://codepen.io/Dillo/pen/gONXJzz) does not load
I tried to load that URL in Chrome and it opened
I captured a profile.

Profile with "network" preset logging : https://share.firefox.dev/3AADRmL

---

This has been happening intermittently for the last few weeks or so.

Comment 1

[Mayank Bansal]

Attachment: about:support

Comment 2

[Kershaw Chang [:kershaw]]

Hi, this seems to be related to HTTP/3. Could you try to capture a http log with selecting the logging preset to HTTP/3 again?
In about:logging, could you please also choose logging to file, since it's easier for me to analyze.
Thanks.

Comment 3

[Mayank Bansal]

Attachment: log.txt-main.18584.zip

Is this log useful?
(Example of a PID that did not load : 16060)

Comment 4

[Kershaw Chang [:kershaw]]

Unfortunately, the log file seems to be incomplete.
I can only see a HTTP/3 connection closed due to idle timeout, but the reason is not clear.

2024-08-19 07:38:01.122000 UTC - [Parent 18584: Socket Thread]: V/nsHttp HttpConnectionUDP::OnQuicTimeoutExpired [this=25d019e8000]
2024-08-19 07:38:01.123000 UTC - [Parent 18584: Socket Thread]: V/nsHttp Http3Session::SendData [this=25d002f1600]
2024-08-19 07:38:01.123000 UTC - [Parent 18584: Socket Thread]: V/nsHttp Http3Session::ProcessOutput reader=25d019e8000, [this=25d002f1600]
2024-08-19 07:38:01.123000 UTC - [Parent 18584: Socket Thread]: I/neqo_transport::* [neqo_transport::connection] [Client b75cac89b66ac952] idle timeout expired

Since we've fixed some issues recently, could you try to reproduce this with Firefox nightly? If you still see this issue, could you try to capture a log again?

Thanks.

Comment 5

[Mayank Bansal]

I have been using/testing on Nightly so i have all the latest changes.

The issue is intermittent. Usually, by the time i realize that the page is not loading, check that Chrome can load, open about:logging, select "http3", and start the logging, the pages start loading.

My ISP has pretty shitty network(150mbps spped but terrible latency and/or dns lookup)

I will keep on testing.

Comment 6

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

Needinfo to the reporter so we'll get pinged when they get a new log and post it

Comment 7

[Mayank Bansal]

I could only get the log in the profiler : https://share.firefox.dev/4dAF38y - PID 26100 . I was trying to open http://codepen.io/kitjenson/pen/MWMGEaE.

Is this useful?

Comment 8

[Mayank Bansal]

Attachment: log.txt-main.16400.zip

Comment 9

[Mayank Bansal]

Here is another profile where i was trying to open https://phabricator.services.mozilla.com/feed/query/all/.
The page did not load in Nightly, but opened in Chrome.

Comment 10

[Kershaw Chang [:kershaw]]

(In reply to Mayank Bansal from comment #9)

Here is another profile where i was trying to open https://phabricator.services.mozilla.com/feed/query/all/.
The page did not load in Nightly, but opened in Chrome.

Sorry for the late reply.

The log file shows that the connection was closed because the server did not respond to the ping message.

2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: V/nsHttp ConnectionEntry::TimeoutTick() this=173844f1f70 host=phabricator.services.mozilla.com idle=0 active=1 dnsAndSock-len=0 pending=0 urgentStart pending=0
2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: I/nsHttp Http2Session::ReadTimeoutTick 17385924e00 delta since last read 66s
2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: I/nsHttp Http2Session::ReadTimeoutTick 17385924e00 handle outstanding ping, timeout=8000
2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: I/nsHttp Http2Session::ReadTimeoutTick 17385924e00 Ping Timer Exhaustion
2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: I/nsHttp Http2Session::Close 17385924e00 804B000E
2024-08-29 09:52:24.665000 UTC - [Parent 16400: Socket Thread]: I/nsHttp Http2Session::CloseStream 17385924e00 173891733a0 0x15 80004004

Unfortunately, there's not much we can do for this case.
So, I'd like to close this bug, but feel free to reopen if you think there's something we should do.
Thanks.