Closed Bug 1811117 Opened 3 years ago Closed 3 years ago

google services like a gmail, search and drive is not loading on Firefox, but works fine on Chrome

Categories

(Core :: DOM: Navigation, defect)

Product:
Core
Component:
DOM: Navigation
Version:
Firefox 109
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: fakezao, Unassigned)

References

Details

Attachments

(3 files)

logs-bugzilla.zip
8.18 MB, application/x-zip-compressed
Details
MOZILLA-NEW-LOGS.txt-main.11508.zip
2.43 MB, application/x-zip-compressed
Details
capture-Mozilla.PNG
13.77 KB, image/png
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36

Steps to reproduce:

  • open Firefox after new installation
  • tried in the search bar open:
    -> drive.google.com
    -> gmail.com
    -> perform a common search like 'promobit'

But if I try openit adding search bar in toolbar, and selecting DuckDuckGo, Bing, it opened the search results, and after clicked on gmail or drive by this way, opened normally.

Actual results:

  • the Google Services is not opening by using search bar on Firefox, but the same behavior is working on Chrome normally.

-> drive.google.com
-> gmail.com
-> perform a common search like 'promobit'

these websites stay loading forever.

The issue is intermittent, sometimes in a day, gmail.com open normal, but drive.com not.

Expected results:

These services and searches is expected to load pages normally by using search bar in both configurations - default and adding search bar in toolbar.

The logs contais sensitive information?
If yes, please remove and tell me how to collect logs in a correct way please.

Any further information let me know to help.
Tthanks in advance.

Attached file logs-bugzilla.zip —

Logs

Please following the video I made just to show the issue

https://drive.google.com/drive/folders/1pA07WSOn-UK0OlXcw41vFB-otBynhjLD?usp=sharing

I'm not able to reproduce this issue using the latest version Firefox 109.0 on Windows 10 x64.
Setting the component so that the developer can have a look.
If this is not the correct component, please feel free to change it to a more appropriate one.

Has STR: --- → yes
Component: Untriaged → Networking: WebSockets
Product: Firefox → Core

An add information is - I'm using a Mozilla Account on browser, that was sync with my Android Phone using firefox.

Thanks for the log!
It shows the http request to drive.google.com and gmail.com are all cancelled because of the reason here.

2023-01-18 21:30:18.424 ⁃ nsHttpChannel ⁃ 1a0f664be00 ⁃ released ⁃ status=804b0002 ⁃ http-status=n/a ⁃ url=https://drive.google.com/
2023-01-18 21:30:22.194000 UTC - [Parent 3956: Main Thread]: D/nsHttp nsHttpChannel::Cancel [this=1a0f664be00 status=804b0002, reason=nsDocLoader::Stop]

2023-01-18 21:30:22.318 ⁃ nsHttpChannel ⁃ 1a0f9b6f100 ⁃ released ⁃ status=804b0002 ⁃ http-status=n/a ⁃ url=https://www.google.com/gmail/
2023-01-18 21:30:29.060000 UTC - [Parent 3956: Main Thread]: D/nsHttp nsHttpChannel::Cancel [this=1a0f9b6f100 status=804b0002, reason=nsDocLoader::Stop]

This looks like not a networking bug, so I'll change the component to DOM:Navigation.

Reporter,
Could you try to record the http log again with adding DocLoader:5 into the MOZ_LOG variable?
This could tell us more information why the document loading is stopped.
Thanks.

Component: Networking: WebSockets → DOM: Navigation
Flags: needinfo?(fakezao)
See Also: → 1760580, 1778892

Hi Kershaw Chang,

Please refer to the new logs attached

Flags: needinfo?(fakezao)
Attached image capture-Mozilla.PNG —

Hi Kershaw Chang,

The image refers to the way I did the new configuration, please check if it's correct.

Flags: needinfo?(kershaw)

(In reply to fakezao from comment #7)

Created attachment 9313317 [details]
capture-Mozilla.PNG

Hi Kershaw Chang,

The image refers to the way I did the new configuration, please check if it's correct.

Yes, that's correct. Thanks.
Note that the cancellation reason is different than the old one.

2023-01-20 18:46:09.578 ⁃ nsHttpChannel ⁃ 1d548eddd00 ⁃ released ⁃ status=804b0002 ⁃ http-status=n/a ⁃ url=https://drive.google.com/
2023-01-20 18:46:13.420000 UTC - [Parent 11508: Main Thread]: D/nsHttp nsHttpChannel::Cancel [this=1d548eddd00 status=804b0002, reason=CanonicalBrowsingContext::CanonicalDiscard]
2023-01-20 18:46:13.420000 UTC - [Parent 11508: Main Thread]: D/nsHttp 1d548eddd00 called from script: chrome://browser/content/tabbrowser.js:4268:14

2023-01-20 18:46:15.899 ⁃ nsHttpChannel ⁃ 1d5497cc100 ⁃ released ⁃ status=804b0002 ⁃ http-status=n/a ⁃ url=https://www.google.com/gmail/
2023-01-20 18:46:20.317000 UTC - [Parent 11508: Main Thread]: D/nsHttp nsHttpChannel::Cancel [this=1d5497cc100 status=804b0002, reason=CanonicalBrowsingContext::CanonicalDiscard]
2023-01-20 18:46:20.317000 UTC - [Parent 11508: Main Thread]: D/nsHttp 1d5497cc100 called from script: chrome://browser/content/tabbrowser.js:4268:14
Flags: needinfo?(kershaw)

Any updates?

the issue still happens here

See Also: → 1818239

Yes, it looks very much like Bug 1818239 could be a duplicate of this, what do you think :smaug?

Flags: needinfo?(afarre) → needinfo?(smaug)

What in this smells similar to Bug 1818239 ? We were discussing about this with peterv and thought these look quite different.

Flags: needinfo?(smaug)
Severity: -- → S2

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

To add another data point:

My experience is precisely the same as the original poster's. I, like him, intermittently experience the symptoms by going directly to Google's sites or performing a Google search. Additionally, I experience the problem intermittently at mail.yahoo.com.

I have a fresh install with a fresh profile and no plugins.

I have attached two logs. log1.txt is me attempting to navigate to travel.google.com, and log2.txt is me attempting to navigate to mail.yahoo.com.

Oops, the logs were too big to attach. You can find them at https://drive.google.com/drive/folders/1VeO3SCmVfLFxsVGX_k3Pl2KLbBTPcSSu

Do you have any extensions installed? Could you try Firefox Troubleshoot mode and see if it reproduces then?

Firefox Troubleshoot mode is basically just starting Firefox from the terminal, like this: firefox -safe-mode.

With that extensions and other customizations will be temporarily turned off for that session, and if it reproduces there we'll be able to know more.

Flags: needinfo?(fakezao)

(In reply to Andreas Farre [:farre] from comment #15)

Do you have any extensions installed? Could you try Firefox Troubleshoot mode and see if it reproduces then?

Firefox Troubleshoot mode is basically just starting Firefox from the terminal, like this: firefox -safe-mode.

With that extensions and other customizations will be temporarily turned off for that session, and if it reproduces there we'll be able to know more.

I will try to reproduce the issue with this mode.

Just FYI, the first attempt that I've collected the logs, was a fresh install with no extensions.

Flags: needinfo?(fakezao)

(In reply to Andreas Farre [:farre] from comment #15)

Do you have any extensions installed? Could you try Firefox Troubleshoot mode and see if it reproduces then?

Firefox Troubleshoot mode is basically just starting Firefox from the terminal, like this: firefox -safe-mode.

With that extensions and other customizations will be temporarily turned off for that session, and if it reproduces there we'll be able to know more.

In Firefox:
Help -> Troubleshoot mode

Tried to reproduce the issue, like access gmail, g drive or a search in the search bar.

All the cases worked properly, and with the troubleshoot mode the issue is not reproducible.

I dont know what is causing the problem, maybe the ADBLOCK
Since you told to test in a troubleshoot mode, and in this way only difference I've noticed is the adblock extension, I removed it.
Since that, outside troubleshoot mode, Firefox is working fine.

The curious case is why after I have a fresh install of firefox, I have the AdBlock installed?

(In reply to fakezao from comment #18)

The curious case is why after I have a fresh install of firefox, I have the AdBlock installed?

The version of adblock used in Chrome is diferent. But work fine on that :(

(In reply to fakezao from comment #19)

(In reply to fakezao from comment #18)

The curious case is why after I have a fresh install of firefox, I have the AdBlock installed?

The version of adblock used in Chrome is diferent. But work fine on that :(

I have installed AdBlock Ultimate again, and the issue is present.
I'm reporting the extension with this bugzilla link.

(In reply to fakezao from comment #20)

(In reply to fakezao from comment #19)

(In reply to fakezao from comment #18)

The curious case is why after I have a fresh install of firefox, I have the AdBlock installed?

The version of adblock used in Chrome is diferent. But work fine on that :(

I have installed AdBlock Ultimate again, and the issue is present.
I'm reporting the extension with this bugzilla link.

Thank you for more tests and confirming, fakezao.
So it sounds we can close this issue on Gecko side.

Close per comment 20.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: