Closed
Bug 411258
Opened 18 years ago
Closed 17 years ago
FF could not connect to the internet after wake up from a sleep on Windows Vista.
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: happyhardik, Unassigned)
References
Details
(Whiteboard: closeme 2009-02-20)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
I have a HP laptop with Windows Vista Home Premium. When I put my computer to sleep with firefox windows open and than when I wake the computer from sleep, firefox is not able to connect to the internet. It shows the waiting mouse pointer like its loading the webpage but nothing loads. And if at the same time you open a webpage in IE, than every thing goes normal. My laptop model is HP dv2214, if that helps.
If you need more details feel free to contact me.
I love FF, please fix this. Thanks.
Reproducible: Always
Steps to Reproduce:
1. Open up few windows in FF (on Windows Vista HP laptop, keep the net connected).
2. Put the computer to sleep and than wake up after some time.
3. oops! firefox could not connect to the internet. keeps on loading the page, and you wait and wait and wait....
Actual Results:
After the wake up the pages are as it is but if you click on any link than the page wont load, firefox will try to load that page but the loading goes on and on.. and nothing loads.
Expected Results:
Open up a page...
nothing.. but if you need you can ask.
Updated•18 years ago
|
Severity: critical → normal
Component: OS Integration → Networking
Product: Firefox → Core
QA Contact: os.integration → networking
Comment 1•18 years ago
|
||
If you exit Firefox while it's in this condition, is it stuck in the Task Manager "Processes" list (firefox.exe)?
Can you run "netstat -b -o > C:\netstat.txt" when this happens and attach the resulting file (C:\netstat.txt) here? You can leave only the lines corresponding to firefox.exe to filter out sensitive information.
(I'm trying to see if the reporter has the same condition that I do on my Vista home premium laptop - I see semi-reproducible loss of network connectivity in trunk Firefox after ~40 minutes uptime - without sleep or hibernation. It's caused by something "closing" one of the loopback sockets used by nsSocketTransportService - so nsSocketTransportService::Poll hangs waiting for a ping via the loopback connection, while any attempt to send the ping in nsSocketTransportService::OnDispatchedEvent gives WSACONNREFUSED)
See also: bug 361060.
In version 2.0.0.12 this bug seems to be fixed!
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Resolution: FIXED → WORKSFORME
Sorry, not fixed. Faced the problem once more.
I tried to run that command netstat but was enable to find the netstat.txt
I have copy-pated what I got on the command prompt.
----------------------------------------------------------------------------
C:\Users\Hardik>netstat -b -o
Active Connections
Proto Local Address Foreign Address State PID
TCP 127.0.0.1:51263 HARDIK-LAPPY:51262 ESTABLISHED 4568
[firefox.exe]
TCP 127.0.0.1:51264 HARDIK-LAPPY:51265 ESTABLISHED 4568
[firefox.exe]
TCP 127.0.0.1:51265 HARDIK-LAPPY:51264 ESTABLISHED 4568
[firefox.exe]
TCP 192.168.1.7:51286 125.252.226.202:http ESTABLISHED 4568
[firefox.exe]
TCP 192.168.1.7:51287 125.252.226.202:http ESTABLISHED 4568
[firefox.exe]
TCP 192.168.1.7:51555 80.239.235.200:https ESTABLISHED 2148
[voipbuster.exe]
TCP 192.168.1.7:51563 cs1:5050 ESTABLISHED 3400
[YahooMessenger.exe]
TCP 192.168.1.7:51622 wf-in-f189:http ESTABLISHED 2376
[iexplore.exe]
TCP 192.168.1.7:51631 sip35:5050 TIME_WAIT 0
TCP 192.168.1.7:51636 f5:http TIME_WAIT 0
-------------------------------------------------------------------------------
And yes, when I close all the windows the process still remains.
This problem is also caused when I run some java (testing) applet and it crash.
I need to manually kill it.
Hope this helps,
Thanks,
Hardik.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
This seems to be a duplicate of 390258. My flash player is up to date, so this does not seem to be the cause of the problem.
Comment 5•18 years ago
|
||
(In reply to comment #3)
> TCP 127.0.0.1:51263 HARDIK-LAPPY:51262 ESTABLISHED 4568 [firefox.exe]
> TCP 127.0.0.1:51264 HARDIK-LAPPY:51265 ESTABLISHED 4568 [firefox.exe]
> TCP 127.0.0.1:51265 HARDIK-LAPPY:51264 ESTABLISHED 4568 [firefox.exe]
Three loopback sessions, event though loopback.
(TCP 127.0.0.1:51262 HARDIK-LAPPY:51263 was lost?)
(In reply to comment #1)
> (snip) nsSocketTransportService::Poll hangs waiting for a ping via the loopback connection, (snip)
Similar phenomenon/problem due to bug of "Outpost Firewall Pro 2.7" was reportd to Bugzilla Japan in the past, although it was problem on MS Win-2K and the problem occurred even with no hibernate/Stand By. In this case, disabling of the firewall software was partial solution - it reduced frequency very much but problem still remained. Complete solution was uninstall of "Outpost Firewall Pro 2.7" followed by install of "Outpost Firewall Pro 4.0".
(We did check log of nsSocketTransport:5 but didn't check session status by)
(netstat. So I don't know about netstat status of our problem. )
To Hardik(bug opener), Nickolay_Ponomarev:
Will "disabling firewall software before Stand By or Suspend" alter situation?
Firewall Software:
I am behind a router and have no additional firewall software on my PC. Vista firewall is disabled. ALL other applications except for Firefox work fine (Outlook, Internet Explorer, ICQ)
Shutting down firefox through Windows task manager and restarting it always solves the problem immediately.
Comment 7•18 years ago
|
||
(In reply to comment #6)
> Shutting down firefox through Windows task manager and restarting it always
solves the problem immediately.
To Phil:
What does "netstat -b -o" say? (before kill of Fx by task manager)
Comment 8•18 years ago
|
||
WADA: Same here (no software firewall / AV, windows fw disabled).
It's interesting that I have this in trunk builds for quite a while (don't have the time to narrow down the "regression" range, if there ever was a code regression), but not in 2.x.
Hardik: could you try a Firefox 3 beta build (installed separately) with a clean profile? And Firefox 2 with a clean profile?
http://developer.mozilla.org/devnews/index.php/2008/03/10/firefox-3-beta-4-now-available-for-download/
http://support.mozilla.com/en-US/kb/Profiles
http://support.mozilla.com/en-US/kb/Managing+profiles
Ok.. I have switch to new profile, which I guess is pretty clean..
Also, I have installed Firefox 3, its great...!
and ya, I had Outpost 2.7 installed on my PC long before but I uninstalled it, as it was not working on vista. My windows firewall is also off.
Is it due to that?
thanks,
happyhardik.
Comment 10•18 years ago
|
||
No firewall software, then too quick wake up for Firefox when Vista?
NSPR logging doesn't have timestamp capability, but when MS Win, timestamp can be obtained by NSPR logging with DebugView. See attached log file to Bug 425897 Comment #13 for example. See Bug 86396 Comment #7 for getting NSPR log with DebugView. See Bug 86396 Comment #15 to get DebugView.
Get NSPR log during Stand By/Quick-Resume(wake up) or Suspend/Resume (hibernation).
(1) Start DebugView(as admin user), stop capture
(2) SET NSPR_LOG_MODULES=all:5
SET NSPR_LOG_FILE=WinDebug
firefox.exe
(3) Enable capture at DebugView
(4) Stand By/Quick-Resume(wake up) or Suspend/Resume
(5) Confirm that problem occurs
(6) Stop capture at DebugView, and save log data to a file
(7) Shutdown Firefox
(8) Teminate DebugView
You can get NSPR log data for step (3) thru (6) only, with timestamp.
Comment 11•18 years ago
|
||
> To Phil:
> What does "netstat -b -o" say? (before kill of Fx by task manager)
This is my netstat result:
Aktive Verbindungen
Proto Lokale Adresse Remoteadresse Status PID
TCP 127.0.0.1:58255 Philip-PC:58254 HERGESTELLT 7352
[firefox.exe]
TCP 127.0.0.1:58256 Philip-PC:58257 HERGESTELLT 7352
[firefox.exe]
TCP 127.0.0.1:58257 Philip-PC:58256 HERGESTELLT 7352
[firefox.exe]
TCP 192.168.178.27:49167 fritz:1012 HERGESTELLT 1500
Dnscache
[svchost.exe]
TCP 192.168.178.27:49191 fk-in-f147:http SCHLIESSEN_WARTEN 2252
[GoogleUpdater.exe]
TCP 192.168.178.27:50355 www:https SCHLIESSEN_WARTEN 2076
[PCSuite.exe]
TCP 192.168.178.27:50357 217-212-246-41:http HERGESTELLT 2076
[PCSuite.exe]
TCP 192.168.178.27:53522 193.254.151.164:http HERGESTELLT 7352
[firefox.exe]
TCP 192.168.178.27:53523 193.254.151.164:http HERGESTELLT 7352
[firefox.exe]
TCP 192.168.178.27:53526 193.254.151.164:https SCHLIESSEN_WARTEN 7352
[firefox.exe]
TCP 192.168.178.27:53531 193.254.151.164:http HERGESTELLT 7352
[firefox.exe]
TCP 192.168.178.27:53532 193.254.151.164:http HERGESTELLT 7352
[firefox.exe]
TCP 192.168.178.27:53542 vlan-132-10-133:26266 HERGESTELLT 4028
Comment 12•18 years ago
|
||
I could see many USB related articles by google search for "Vista loopback".
And Bug 404287 Comment #28 has reported problem relates to USB device on Vista.
> USB device for readyboost with Vista Home Basic and with Vista Home Premium
"Vista Home" only issue? USB related issue?
| Reporter | ||
Comment 13•18 years ago
|
||
Hello,
I have started using firefox 3 beta 5 with a clean profile and finally.. found that this problem is still there.
The only difference that I noticed was of the way it behaved, till now in firefox 2 the waiting mouse pointer was seen, now when I am trying to open a web page it does some kind of processing and than says done and nothing opens..
I am right now I am using IE to connect to this site and firefox is hanged with lot of windows and tabs opened.
Here is my netstat result:
C:\Users\Hardik>netstat -o -b
Active Connections
Proto Local Address Foreign Address State PID
TCP 127.0.0.1:50543 HARDIK-LAPPY:50544 ESTABLISHED 3748
[firefox.exe]
TCP 127.0.0.1:50544 HARDIK-LAPPY:50543 ESTABLISHED 3748
[firefox.exe]
TCP 127.0.0.1:50546 HARDIK-LAPPY:50547 ESTABLISHED 3748
[firefox.exe]
TCP 127.0.0.1:50547 HARDIK-LAPPY:50546 ESTABLISHED 3748
[firefox.exe]
TCP 127.0.0.1:50578 HARDIK-LAPPY:50579 ESTABLISHED 3092
[thunderbird.exe]
TCP 127.0.0.1:50579 HARDIK-LAPPY:50578 ESTABLISHED 3092
[thunderbird.exe]
TCP 127.0.0.1:50580 HARDIK-LAPPY:50581 ESTABLISHED 3092
[thunderbird.exe]
TCP 127.0.0.1:50581 HARDIK-LAPPY:50580 ESTABLISHED 3092
[thunderbird.exe]
TCP 192.168.1.11:2869 DEVICE1:3997 ESTABLISHED 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 192.168.1.11:51020 216.213.38.178:http CLOSE_WAIT 4788
[iexplore.exe]
TCP 192.168.1.11:51029 216.213.39.250:http CLOSE_WAIT 4788
[iexplore.exe]
TCP 192.168.1.11:51030 im-in-f104:http CLOSE_WAIT 4788
[iexplore.exe]
TCP 192.168.1.11:51337 *Server Name*:ms-wbt-server ESTABLISHED 5
076
[mstsc.exe]
TCP 192.168.1.11:51875 24-117-45-50:42312 ESTABLISHED 452
[Skype.exe]
TCP 192.168.1.11:51905 205.188.8.189:5190 ESTABLISHED 4612
[pidgin.exe]
TCP 192.168.1.11:51906 by1msg2245406:msnp ESTABLISHED 4612
[pidgin.exe]
TCP 192.168.1.11:51908 caim-m04b:5190 ESTABLISHED 4612
[pidgin.exe]
TCP 192.168.1.11:51909 205.188.13.40:5190 ESTABLISHED 4612
[pidgin.exe]
TCP 192.168.1.11:51933 im-in-f104:http ESTABLISHED 3032
[iexplore.exe]
TCP 192.168.1.11:51939 dsl-mum-erx-138:http ESTABLISHED 3032
[iexplore.exe]
TCP 192.168.1.11:51940 dsl-mum-erx-138:http ESTABLISHED 3032
[iexplore.exe]
TCP 192.168.1.11:51941 dsl-mum-erx-137:http ESTABLISHED 3032
[iexplore.exe]
TCP 192.168.1.11:51943 *server name*:netbios-ssn ESTABLISHED 4
Can not obtain ownership information
x: Windows Sockets initialization failed: 5
TCP 192.168.1.11:51944 *server name*:netbios-ssn TIME_WAIT 0
TCP 192.168.1.11:51945 165.228.129.10:3128 SYN_SENT 2324
wuauserv
[svchost.exe]
TCP 192.168.1.11:51946 116.2.223.195:42584 SYN_SENT 452
[Skype.exe]
Comment 14•17 years ago
|
||
fwiw, this problem (comment 1) fixed itself for me sometime before fx3.
Comment 15•17 years ago
|
||
Hrdik's first case of comment #3.
> Proto Local Address Foreign Address State PID
> TCP 127.0.0.1:51263 HARDIK-LAPPY:51262 ESTABLISHED 4568 [firefox.exe]
> TCP 127.0.0.1:51264 HARDIK-LAPPY:51265 ESTABLISHED 4568 [firefox.exe]
> TCP 127.0.0.1:51265 HARDIK-LAPPY:51264 ESTABLISHED 4568 [firefox.exe]
"TCP 127.0.0.1:51262 HARDIK-LAPPY:51263" looks to be lost.
Phil's case in comment #11.
> Proto Lokale Adresse Remoteadresse Status PID
> TCP 127.0.0.1:58255 Philip-PC:58254 HERGESTELLT 7352 [firefox.exe]
> TCP 127.0.0.1:58256 Philip-PC:58257 HERGESTELLT 7352 [firefox.exe]
> TCP 127.0.0.1:58257 Philip-PC:58256 HERGESTELLT 7352 [firefox.exe]
"TCP 127.0.0.1:58254 Philip-PC:582555 looks to be lost.
Hrdik's second case in to comment #13.
> Proto Local Address Foreign Address State PID
> TCP 127.0.0.1:50543 HARDIK-LAPPY:50544 ESTABLISHED 3748 [firefox.exe]
> TCP 127.0.0.1:50544 HARDIK-LAPPY:50543 ESTABLISHED 3748 [firefox.exe]
> TCP 127.0.0.1:50546 HARDIK-LAPPY:50547 ESTABLISHED 3748 [firefox.exe]
> TCP 127.0.0.1:50547 HARDIK-LAPPY:50546 ESTABLISHED 3748 [firefox.exe]
> TCP 127.0.0.1:50578 HARDIK-LAPPY:50579 ESTABLISHED 3092 [thunderbird.exe]
> TCP 127.0.0.1:50579 HARDIK-LAPPY:50578 ESTABLISHED 3092 [thunderbird.exe]
> TCP 127.0.0.1:50580 HARDIK-LAPPY:50581 ESTABLISHED 3092 [thunderbird.exe]
> TCP 127.0.0.1:50581 HARDIK-LAPPY:50580 ESTABLISHED 3092 [thunderbird.exe]
No loopback connection loss is seen.
(In reply to comment #13.
To Hardik(bug opener):
Your problem in comment #13 looks for me to be different from problem of comment #1 & #3 & #11.
Comment 16•17 years ago
|
||
(In reply to comment #15)
> To Hardik(bug opener):
> Your problem in comment #13 looks for me to be different from problem of
> comment #1 & #3 & #11.
is it even possible to test whether problem of comment 0 is gone?
Whiteboard: closeme 2009-02-20
| Reporter | ||
Comment 17•17 years ago
|
||
Hi,
Now, I haven't received any problems since a long time?
Is it gone?
I am using: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Comment 18•17 years ago
|
||
=> WFM per comment 17
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•