Closed Bug 1360008 Opened 7 years ago Closed 7 years ago

firefox 53.0 stops making internal and external connections - hung - win7 64bit

Categories

(Core :: Networking, defect)

53 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1360574

People

(Reporter: austin.osterhout, Assigned: u408661)

Details

(Whiteboard: [necko-active])

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170413192749

Steps to reproduce:

user agent: "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
use or leave firefox open for a while


Actual results:

all connections drop, can't reload, can't visit new page.  

can open new tabs, but can't make connections to internet, or sites local to domain.

netstat -b results for firefox when frozen:

[firefox.exe]
 TCP    127.0.0.1:60109        mis-ao-w7:60108        TIME_WAIT
[firefox.exe]
 TCP    127.0.0.1:60113        mis-ao-w7:60111        TIME_WAIT
[firefox.exe]
 TCP    127.0.0.1:60086        mis-ao-w7:60085        TIME_WAIT
[firefox.exe]
 TCP    127.0.0.1:60089        mis-ao-w7:60088        TIME_WAIT


Expected results:

firefox should work well like firefox usually does.

close and reopen firefox "fixes" the issue, until it happens again.
one user had the previous user agent, but many users affected have the following:

"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53."
Also happens on my win7 pro 64bit workstation as well.

"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0"

all workstations affected here are win7pro 64 so far.  we have some win10, but haven't heard of any issues yet.

For now, rolling all workstations back to 52.0.1 until we can resolve.

-austino
Component: Untriaged → Networking
Product: Firefox → Core
Update:

Now using Firefox 52.0.1 (testing before rollout to others with issue).
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0"

In firefox 52.0.1 now, I am noticing that I get a similar issue (though not completely the same):
- after a while (unspecified time) firefox will not connect to google.com, nor will google search bar make connection with internet.  seems to be any other site works when typed in to the address bar, and any other search engine searchbar will work as well (such as duckduckgo)

hope this helps?

-austino
Update:

Now using Firefox 52.0.1 
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0"

Left browser open overnight, have no issues this morning using google searchbar, or going to google.

deployed 52.0.1 to rest of machines in the fleet for now, until further testing of 53.0 (or update) on win7pro 64bit.

-austino
Austin, are you perhaps using an NTLM proxy? Either way, could we get an HTTP log of this happening? Instructions at https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Using_aboutnetworking

Thanks!
Flags: needinfo?(austin.osterhout)
Attached file mzlog_tail.txt
it is using squid on debian stable with negotiate and kerberos

tail of log file attached (please note that I had to chop this down to send it.)

I still have the full original if we need to go back further.  

-austino
Flags: needinfo?(austin.osterhout)
(In reply to Nicholas Hurley [:nwgh][:hurley] (also hurley@todesschaf.org) from comment #5)
> Austin, are you perhaps using an NTLM proxy? Either way, could we get an
> HTTP log of this happening? Instructions at
> https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/
> HTTP_logging#Using_aboutnetworking
> 
> Thanks!

I can confirm at my work two people (including myself) have the same issue, using an NTLM proxy. I'll try to get an HTTP log also but the problem is intermittent. Would it help to take a process dump while FF is in the bad state, or something similar? I tried starting over with a new profile and it didn't help. My colleague rolled back to 52.0.2 and has been problem free for a few days
(In reply to Jeff Martin from comment #7)
> (In reply to Nicholas Hurley [:nwgh][:hurley] (also hurley@todesschaf.org)
> from comment #5)
> > Austin, are you perhaps using an NTLM proxy? Either way, could we get an
> > HTTP log of this happening? Instructions at
> > https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/
> > HTTP_logging#Using_aboutnetworking
> > 
> > Thanks!
> 
> I can confirm at my work two people (including myself) have the same issue,
> using an NTLM proxy. I'll try to get an HTTP log also but the problem is
> intermittent. Would it help to take a process dump while FF is in the bad
> state, or something similar? I tried starting over with a new profile and it
> didn't help. My colleague rolled back to 52.0.2 and has been problem free
> for a few days

Is this the same behavior as described in bug #1360574?
(In reply to will69 from comment #8)
> (In reply to Jeff Martin from comment #7)
> > (In reply to Nicholas Hurley [:nwgh][:hurley] (also hurley@todesschaf.org)
> > from comment #5)
> > > Austin, are you perhaps using an NTLM proxy? Either way, could we get an
> > > HTTP log of this happening? Instructions at
> > > https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/
> > > HTTP_logging#Using_aboutnetworking
> > > 
> > > Thanks!
> > 
> > I can confirm at my work two people (including myself) have the same issue,
> > using an NTLM proxy. I'll try to get an HTTP log also but the problem is
> > intermittent. Would it help to take a process dump while FF is in the bad
> > state, or something similar? I tried starting over with a new profile and it
> > didn't help. My colleague rolled back to 52.0.2 and has been problem free
> > for a few days
> 
> Is this the same behavior as described in bug #1360574?

Yes, appears to be exactly the same. When I got up to ~700 active sessions to this page Firefox entered the bad state.
in case it is helpful

Another tail of a new log file.  

closed all tabs but one
started logging
Forced Firefox to freeze by refreshing (ctrl+f5) page roughly 30 times.
stopped loging

took the tail of the log (log was over 250MB, so couldn't send the whole thing)

-austino
Assignee: nobody → hurley
Flags: needinfo?(hurley)
Whiteboard: [necko-active]
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(hurley)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: