Firefox enters a state where all http requests never finish
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: kael, Unassigned)
Details
Attachments
(1 file)
|
358.62 KB,
image/png
|
Details |
Earlier today Firefox Nightly (97.0b2 64-bit, I think the update installed today or yesterday?) entered a state where all HTTP requests would hang and never complete, across the entire browser. Existing assets could be loaded from cache by webpages, and uBlock could successfully block outgoing requests, but any other HTTP(s) requests would just start and never finish. Devtools showed no headers or timing or other information for all the requests, but they would show up in the log, like in the attached screenshot.
This applied to all websites in both new and existing tabs, across both HTTP and HTTPS.
Sometimes restarting the browser would make it go away, but sometimes it would 'stick' across restarts. I had it come back at least twice over the course of the last couple hours. During this time period, Edge works perfectly fine as does all the other networked software on my PC, only Firefox is broken.
This also causes existing streaming content (like YouTube) to fall over because it is no longer able to fetch new media chunks.
If I close Firefox in this state, all the firefox.exe processes hang indefinitely in the background even though all the windows are closed and then eventually get murdered by the hang detector (https://crash-stats.mozilla.org/report/index/ab53e0d1-6ba6-4b02-8815-f626b0220113 is one of them, I think)
Troubleshooting steps I tried:
- Starting with all addons disabled
- Disabling IPv6
At first I thought disabling addons had made it go away, but then it reoccurred with my addons all shut off, and I can successfully re-enable all my addons without making it happen if I turn them on while the browser is still working.
| Reporter | ||
Comment 1•4 years ago
|
||
It happened again so I turned on network logging under about:networking and it produced around a gigabyte of log messages in the 1-2 minutes I left it enabled for. The messages seem to all be this:
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=350 state=4 [this=29050b7e660]
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp nsHttpTransaction::ReadRequestSegment 29030ec3800 read=0
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=350 state=4 [this=29050b7e660]
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp nsHttpTransaction::ReadRequestSegment 29030ec3800 read=0
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=350 state=4 [this=29050b7e660]
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp nsHttpTransaction::ReadRequestSegment 29030ec3800 read=0
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=350 state=4 [this=29050b7e660]
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp nsHttpTransaction::ReadRequestSegment 29030ec3800 read=0
2022-01-13 09:06:58.091000 UTC - [Parent 20324: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=350 state=4 [this=29050b7e660]
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Description
•