HTTP GET hangs infinitely

UNCONFIRMED
Unassigned

Status

()

Core
Networking: HTTP
P3
normal
UNCONFIRMED
7 months ago
3 months ago

People

(Reporter: Andy, Unassigned)

Tracking

53 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog])

(Reporter)

Description

7 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170504105526

Steps to reproduce:

I was browsing the internet in Firefox and lost all ability to access any site anywhere. This issue was entirely restricted to Firefox. URLs Firefox failed to load - or rather, hung infinitely without producing a sensible error message - loaded instantly in every non-Firefox browser on the same PC.


Actual results:

I clicked on a link and Firefox displayed a blank screen with an animated circle in the middle for approximately 90 minutes. At various points I tried opening new tabs with multiple other random URLs and all hung at the same blank screen, spinning circle indefinitely. Accessing the exact same URLs in Chrome or Edge worked 100% of the time.


Expected results:

Firefox should have loaded the clearly accessible sites OR given some kind of error message within at most 30-60 seconds. Trying to load a site with no user feedback for over an hour is insane.

Updated

7 months ago
Component: Untriaged → Networking: HTTP
Product: Firefox → Core

Comment 1

7 months ago
Bugzilla is not support forum.
Please go to https://support.mozilla.org/en-US/products/firefox .
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → INVALID
(Reporter)

Comment 2

7 months ago
It's not a support request. Closing and re-opening Firefox fixed the issue. Having the browser enter a state where it's completely incapable of browsing the web without restarting the application is presumably a bug rather than intended behavior.
Are you using an NTLM proxy?
Flags: needinfo?(andy)

Comment 4

7 months ago
(In reply to Andy from comment #2)
> Closing and re-opening Firefox fixed the issue.

Ah, that is weird. Seems bug of Firefox.

And, Did previous version of Firefox(such as Firefox52, 51) work for you?
If so, Could you use the tool mozregression to narrow down a regression range in FF53, please.

See http://mozilla.github.io/mozregression/ for details.
Run the command "mozregression --good=52" or "mozregression --good=51" then for each build, make the test and enter if it's good or bad, then copy here the final pushlog.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Whiteboard: [necko-backlog]
(Reporter)

Comment 5

7 months ago
Sorry about the delay. No, I'm not running an NTLM proxy.

Running mozregression didn't really help since I don't have any reliable repro test case. I fully realize random catastrophic failure isn't exactly easy to debug but the "catastrophic" part makes it seem work reporting.

I did experience the exact same issue today on a different PC (FF 53.0.3, 32-bit, Win10 x64) from the one that led to the initial report. The failure case was identical. Entering any URL in the address bar showed a spinning circle indefinitely (hours) without succeeding or erroring. Restarting the browser promptly restored its ability to be a web browser.
Flags: needinfo?(andy)
(Reporter)

Comment 6

7 months ago
Sorry about the delay. No, I'm not running an NTLM proxy.

Running mozregression doesn't help since I don't have any reliable repo test case. I realize random catastrophic failure is difficult to debug but the "catastrophic" part makes it seem worth reporting.

I experienced a similar seeming issue today on different hardware (FF 53.0.3 x86, Win10x64). Entering any address displayed a blank white screen seemingly forever (hours) without loading a site or displaying an error or any other kind of feedback. Restarting Firefox again immediately restored its ability to be a functional web browser.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.