Closed Bug 1629090 Opened 5 years ago Closed 5 years ago

Gmail keeps going into offline mode (and other issues with Google)

Categories

(Core :: Networking: HTTP, defect, P1)

77 Branch
defect

Tracking

()

VERIFIED FIXED
mozilla77
Tracking Status
firefox-esr68 --- unaffected
firefox75 --- unaffected
firefox76 --- unaffected
firefox77 blocking verified

People

(Reporter: mccr8, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [necko-triaged])

I'm using Nightly. In the last day or two, I started having issues where it keeps saying "You're offline. Results may be limited.". Some images, like the gmail logo at the upper left and the plus next to "compose" on the left sometimes fail to load. Reloading the page helps, but it soon goes into offline mode. I was inclined to blame my ISP, but Gmail loaded in Chrome seems to be just fine.

[Tracking Requested - why for this release]: Gmail not working is bad.

I don't know if this is just me, but :aki said he was seeing the same thing, on Slack.

For the images that don't load, if I right click on them and do "load image" they load up immediately. (In a new tab of course.)

Perhaps related, I’ve also had issues loading utm urls. Once I strip the google.com/url and other query string bits from the url, I can load the target url just fine.

I'm trying to use MozRegression to narrow down when this might have started happening, if it is actually a Firefox-side issue, but it takes a while to reproduce, so it is a little hard to say if it is really happening or not at any given moment. Force reloading seems to have fixed the broken image issue I had. Maybe having multiple gmails open at once (my personal + my MoCo accounts) is required for it to happen?

Summary: Gmail keeps going into offline mode → Gmail keeps going into offline mode (and other issues with Google)
Component: Untriaged → Privacy: Anti-Tracking
Product: Firefox → Core
Regressed by: 1610373

Google Docs is having trouble loading for me, too.

I've seen another 2 or 3 people report similar problems in Slack. We should probably back out bug 1610373.

Bug 1610373 has been backed out. Hopefully this problem will be fixed in the next Nightly in a few hours.

I doubt that bug is the reason because in that bug I introduce a new method which is not used yet.

I'll try to do another bisection.

Here's a slightly wider range I got in the middle: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=75323c5f1047c579989b6a0dabd8fa29c854c869&tochange=33d2485721c6ffd20a952d698754041a14be11b3

I will note that "Turn on HTTP/3 on Nightly" is in there, and that seems like a big change that could cause issues when loading things...

For what it's worth, I've seen the problem with Gmail randomly for a while (months), but I haven't been able to reproduce it reliably.

Sometimes it happens after a browser restart, others after I get my mac out of sleep, and I realize it only when I click on a label (the inbox, or the currently viewed label would look normal, no sign of being offline).

EDIT: I've found my own message on Slack where I was asking if others were seeing this issue, it's from end of October. I confess I haven't seen it for a while, but it happened again in the last couple of days.

I flipped the network.http.http3.enabled pref to false, and will report back if I see the issue again.

A more consistent STR for me seems to be loading docs.google.com. In the bad case, it'll fail during loading with "No connection" almost immediately, I think.

A second round of mozregression pointed at bug 1628461, but now I can't reproduce the issue at all in my profile on the latest Nightly.

Sorry for the bad regression range, Baku. I guess I did something wrong when it got down to the very last step and took the wrong split at a bisection branch. I should have looked at the patch first.

No longer regressed by: 1610373

Dragana, this is a possible regression from bug 1628461 that you might want to see, though the repro steps are a bit finicky so it is hard to say for sure.

Flags: needinfo?(dd.mozilla)

I mozregressed another time and it again pointed to bug 1628461. I'm sometimes able to reproduce the symptoms (things like Google Docs not fully loading, icons not all loading on Gmail) with http3 enabled, but not disabled, but sometimes it loads just fine, so I'm not sure.

Http/3 is turned off again (in the next Nightly build). Can you send me a http log. It will contain cookies and URIs. probably grepping for Http3Session and Http3Stream will be enough logging to see what is happening. Please look at the log if it still contains cookies and uris (I am not sure.)

google is not advertising http3 for me.

Flags: needinfo?(dd.mozilla) → needinfo?(continuation)
Blocks: QUIC
Component: Privacy: Anti-Tracking → Networking: HTTP
Priority: -- → P1
Whiteboard: [necko-triaged]

Disabled in bug 1629057

I've emailed you the log.

Flags: needinfo?(continuation)

From the log:

we successfully finish handshake. We send some request, we receive just a single small packet and nothing else. We do not get any response from the server. We retransmit packets but we are not receiving anything.

Other connection to google using http3 work fine.

FWIW I was hitting intermittent -- but consistent for long stretches of time -- problems with Google stuff (search results pages would immediately show "Timed out" network error pages, filling out a survey wouldn't load all stylesheets, trying to switch accounts to fill out that survey wouldn't load all images and trying to click on a different account wouldn't switch logins right) with HTTP 3 enabled. I was also hitting problems doing image uploads as comments on Facebook -- uploading a 317K image would get around 30K into the POST of it and not complete.

Flipping the network.http.http3.enabled pref immediately made all those work consistently. :-|

Fixed by backout.

Assignee: nobody → dd.mozilla
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
Version: unspecified → 77 Branch

This bug is tracked by a release manager but with a small severity so change it to major.
For more information, please visit auto_nag documentation.

Severity: normal → major
Flags: qe-verify+

Reproduced the initial issue using an old Nightly build from 2020-04-10, verified that this is fixed using latest Firefox Beta 77.0b9 across platforms (macOS 10.15, Windows 10 64bit and Ubuntu 18.04 64bit).

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.