1891649 - Webpage sometimes auto stop loading

Status: UNCONFIRMED

(Core :: Networking, defect, P3)

Description

[Tom25519]

I don't know if it related to I set network.http.connection-retry-timeout = 0

Comment 1

[Tom25519]

Attachment: 2024-04-15 22-59-10.mp4

Comment 2

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

Can you retry with that set to 250 (the default)?

Also can you get network logs: go to about:logging, capture logs with a Networking preset, and email to [e-mail]? Please reference this bug in your email.

Thanks!

Comment 3

[Tom25519]

I try to reproduce it on a VM by set packet loss rate and delay. Some conditions:

1. High packet loss rate (gov's censorship interfere).
2. Crowded upload bandwith (eMule and Bitcomet consume almost all my upload bandwith).
3. High network delay (No datacenter of Github in my country).

Unfortunately, due to poor network in vm, Firefox profiler website also couldn't load.

Comment 4

[Tom25519]

Attachment: log.txt-main.5248.moz_log

Comment 5

[Tom25519]

VM network setting (Outbound&Inbound):

Packet loss rate: 25%
Delay: 250 ms

By the way, I have been revert network.http.connection-retry-timeout to default.

Comment 6

[Tom25519]

Attachment: log.txt-main.8552.zip

Comment 7

[Tom25519]

It happens again on my real PC.

Comment 8

[Kershaw Chang [:kershaw]]

I saw this error from this log (log.txt-main.8552.zip).

2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport nsSocketInputStream::Read [this=20afae21f00 count=9]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport   calling PR_Read [count=9]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport   PR_Read returned [n=-1]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport ErrorAccordingToNSPR [in=-5961 out=804b0014]

It looks like that the connection was reset by the server side (or somewhere in the middle).
Unfortunately, there isn't much we can do about this.

Does this still happen if you change your network (via VPN)?

Comment 9

[Tom25519]

(In reply to Kershaw Chang [:kershaw] from comment #8)

I saw this error from this log (log.txt-main.8552.zip).

2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport nsSocketInputStream::Read [this=20afae21f00 count=9]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport   calling PR_Read [count=9]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport   PR_Read returned [n=-1]
2024-04-16 10:21:20.262000 UTC - [Parent 8552: Socket Thread]: D/nsSocketTransport ErrorAccordingToNSPR [in=-5961 out=804b0014]

It looks like that the connection was reset by the server side (or somewhere in the middle).
Unfortunately, there isn't much we can do about this.

Oh! I think it may caused by gov's internet censorship firewall!

Does this still happen if you change your network (via VPN)?

In fact, this bug not always happened, and I wonder why firefox doesn't show an error page (connection reset?) instead of a blank page?

Comment 10

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

We can probably improve our error page when the connection is reset.