433199 - After resuming from hibernate, browsers acts like there's no network connection

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[Troodon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008050901 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008050901 SeaMonkey/2.0a1pre

 

Reproducible: Always

Steps to Reproduce:
1. Hibernate.
2. Resume.
3. Try to load a new page in browser.
Actual Results:  
Browser works like there is no network connection, so is not able to load any remote page. After closing it, it stays on memory, so you have to close it with the task manager.


This happens with both Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008050901 SeaMonkey/2.0a1pre and Mozilla/5.0 (Windows; U; Windows NT 6.0; es-ES; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 on Windows Vista, so it's a Core bug.

I've searched for similar bugs, but only found old bugs for Gecko 1.8 (FF 2.X) and Windows XP that are marked as fixed.

Comment 1

[WADA:World Anti-bad-Duping Agency]

> on Windows Vista
Sounds to be similar issue to Bug 411258 or Bug 419541.
What does "netstat -b -o" say? Loss of loopback connection after hibenattion?

Comment 2

[Troodon]

I have seen this happening sometimes after waking suspend, too. netstat shows only three loopback connections, which means one is lost. I suspect this could be a firewall-related problem, but I have to investigate further before closing this bug.
Thank you for your help!

Comment 3

[Shira.inusyl]

I'm experiencing the same problem. After the computer resumes from sleep or hibernation, it's impossible to use the address bar. Typing in addresses or clicking the drop-down results accomplishes nothing; Firefox simply sits there and acts as though nothing were clicked. However, if I click on a link in an already-opened page, the browser responds normally. Closing and restarting Firefox solves the problem. I haven't had to use the task manager to forcibly terminate the process; clicking file -> exit has been enough to close the browser in my case, unlike in the original bug report.

I'm also using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0

Comment 4

[WADA:World Anti-bad-Duping Agency]

Setting dependency to Bug 411258, based on Comment #2.

To Troodon(bug opener) and Shira.inusyl:

Get NSPR log with time stamp, if your problem is re-creatable. See Bug 411258 Comment #10 for getting log with time stamp.

Comment 6

[Tony Mechelynck [:tonymec]]

Bug 459801 is the same symptom seen by another user on Sm 1.1.12, so confirming.

Comment 7

[Troodon]

Still having this problem with both FF 3.5.3 and SM 2.0B2. When I'll have some time, I'll try to get a NSPR log as suggested in comment #4.

Comment 8

[Ed Morley [:emorley]]

Do you still see this issue with Firefox 3.6.13 or later / SeaMonkey 2.1 Beta 1 or later, in safe mode:
http://support.mozilla.com/kb/Safe+Mode

How about in Firefox 4 Beta 8 or later:
http://www.mozilla.com/en-US/firefox/all-beta.html

(In reply to comment #7)
> I'll try to get a NSPR log as suggested in comment #4.
Any luck in getting this?

Comment 9

[Wayne Mery (:wsmwk)]

Shira isn't using firefox any more.
no response from reporter
=> incomplete  (although it does work for me)