866693 - Tabs "Connecting..." for a very long time after startup

Status: RESOLVED INCOMPLETE

(Core :: Networking, defect)

Description

[Johnny]

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130409194949

Steps to reproduce:

Every time I start up Firefox and try to navigate to a web page.


Actual results:

It will be stuck on "Connecting..." for about 10 seconds before actually connecting to the page. Once this first page is loaded, other pages load quickly as per usual, it's only for the first thing that I load after opening Firefox.


Expected results:

It should only be "Connecting..." for a second or two before loading the page.

Comment 1

[[:Aleksej]]

DNS?

Do you have a proxy, or a DNS server IP that is firewalled off?

Comment 2

[Johnny]

Nope

Comment 3

[Johnny]

(In reply to Aleksej [:Aleksej] from comment #1)
> DNS?
> 
> Do you have a proxy, or a DNS server IP that is firewalled off?

Nope

Comment 4

[Jason Duell]

Does this happen with other browsers on your machine, or just Firefox?  Just trying to do a quick sanity check that this isn't some weirdness with your network.

Comment 5

[Johnny]

(In reply to Jason Duell (:jduell) from comment #4)
> Does this happen with other browsers on your machine, or just Firefox?  Just
> trying to do a quick sanity check that this isn't some weirdness with your
> network.

Just Firefox unfortunately :(

If I have my home page set to a specific site, the home page will be loaded fairly quickly (~5 sec). If, immediately after I start Firefox, I open a new tab and try to navigate to another site, it will take about 10-15 seconds for it to be done "Connecting..." before it loads.

Comment 6

[Jason Duell]

When I open my many-tabbed browser session and immediately open a new tab, I can load things in it quickly.  I'm not sure what's different about j0hnny_07's situation that makes it pause for 10 sec.   My understanding is that we bump the priority on the foreground tab's network channels, so as soon as there are free connection slots (i.e. we're not at max-connection limit) we ought to immediately open the channel(s) for the new tab you've opened.  It's odd that it would take 10-15 seconds for one or more of the many (usually 256, but sometime 64 on windows) HTTP connections to not free up within a second or two.

You could try opening about:config and setting "network.http.max-connections" to something greater than 256.  I'd be surprised if it helps, but you never know...

Comment 7

[Johnny]

(In reply to Jason Duell (:jduell) from comment #6)
> When I open my many-tabbed browser session and immediately open a new tab, I
> can load things in it quickly.  I'm not sure what's different about
> j0hnny_07's situation that makes it pause for 10 sec.   My understanding is
> that we bump the priority on the foreground tab's network channels, so as
> soon as there are free connection slots (i.e. we're not at max-connection
> limit) we ought to immediately open the channel(s) for the new tab you've
> opened.  It's odd that it would take 10-15 seconds for one or more of the
> many (usually 256, but sometime 64 on windows) HTTP connections to not free
> up within a second or two.
> 
> You could try opening about:config and setting
> "network.http.max-connections" to something greater than 256.  I'd be
> surprised if it helps, but you never know...

Yeah, as you suspected that didn't work. Thanks for your help though

Comment 8

[Patrick McManus [:mcmanus]]

I'm going to close this as long idle and not actionable.

if this is still an issue for you, please add a https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging to the bug and reopen - we can make progress with that