1619634 - On First opening Firefox, the software hangs for 10 to 20 seconds when anthing is entered into the address bar

Status: RESOLVED INCOMPLETE

(Firefox :: Address Bar, defect, P3)

Description

[William Spratt]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

We have Firefox 68.5.0ESR. Installed using the .msi file via SCCM. We have a proxy server. GPO sets the following:
We can then set the following policies:
• Set the ImportEnterpriseRoots key to true.
• Under Proxy, set “Mode” to “autoDetect”
• DisableAppUpdate to true
• Under Homepage, setting URL to [intranet page], and StartPage to “homepage”
• Under PopupBlocking, setting “allow” to [intranet page];
• Under FlashPlugin, setting “allow” to [intranet page]
• Under OverrideFirstRunPage, set to Blank, so it will default to the homepage
• Under OverridePostUpdatePage, set to Blank, so it will default to the homepage

Actual results:

After start up, anything entered into the address bar followed by enter will cause the tab to go white and hang for about 10 to 20 seconds. It doesn't seem to matter if hardware acceleration is turned on or off. It doesn't seem to matter whether it be a bookmark shortcut, a search term or and actual address (in the format "www.google.com"). For a few minutes after the initial tab is resolved, there is no hanging. Then after a period of inactivity for Firefox, the hanging is observed again.

Expected results:

Page to resolve immediately, as they do in Edge or Chrome.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

Could you please test if changing your DNS server temporarily helps with this?

If I understand correctly, it's not the urlbar that is hanging when you use it, but the first page load, is that correct? If you set the default homepage to an actual Web Page, does it hang when you open Firefox?

Comment 3

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

Also, when you say hanging, you mean the application is blocked completely (UI doesn't react if you click buttons and such) or just doing nothing but stays responsive?

Comment 4

[William Spratt]

The UI isn't blocked completely. It stays responsive. Testing the other questions.

Comment 5

[William Spratt]

We use two internal DNS servers, and multiple people have had the issue, some using one and some using the other, yet edge and chrome on their machines are unaffected. We could set up a new VM as a DNS server if you need us to, but I don't think that's the trigger.

The first page load is affected, yes, but it's not the only thing. If you try another page (i.e. from a link or bookmark) or a search immediately after the initial load page has loaded, the next page (or search) loads immediately. If you wait a few minutes (reading a web page or doing something else) the issue manifests again.

Testing if changing the homepage triggers a different behaviour.

Comment 6

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

Could you also test with an external DNS, just to understand if there's a relation with your DNS setup.

Comment 7

[William Spratt]

What DNS would you recommend?

Also, changing the startup page to an external site (like https://www.bbc.co.uk/news) has made no difference.

Comment 8

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

any fast public dns, cloudflare, google, any of them, just to see if bypassing your internal dns changes anything.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:adw, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 10

[Drew Willcoxon :adw]

William, any luck trying Marco's suggestion (pasted below)?

(In reply to Marco Bonardo [:mak] from comment #8)

any fast public dns, cloudflare, google, any of them, just to see if bypassing your internal dns changes anything.

Comment 11

[-]

[redacted - mhoye]

Comment 12

[Drew Willcoxon :adw]

No response in over a year and there's not much actionable here, so I'll close this.

William, if you're able to address Marco's suggestion, please comment here.