Closed
Bug 406457
Opened 18 years ago
Closed 10 years ago
On network change from WiFi to ethernet FireFox hangs (IE works) - I had to Restart Firefox to work
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: etechship, Unassigned)
References
Details
(Whiteboard: [lame-network])
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 am running Windows Vista Home Prem. 32 bit.
I have heard about the standby issue, but my laptop doesn't go into standby.
Reproducible: Always
Steps to Reproduce:
1. Boot up computer and connect to wifi router (Internet works fine here)
2. Connect ethernet cable to laptop
3. disconnect from WiFi and wait for the ethernet connection to get DHCPed
Actual Results:
I will have at least one, if not to more, tabs open. I will try to refresh a page, or open a new page and the page(s) will lock up. It will not display the "site no found" yellow screen.
Expected Results:
The page(s) should reload, or load, perfectly.
I have no extra themes or addons that I use or have installed in Firefox. I have the latest edition (2.0.0.11).
I have a Acer 5610 laptop, Windows Vista Home Prem. 32 Bit.
Updated•18 years ago
|
Component: Session Restore → Networking
Product: Firefox → Core
QA Contact: session.restore → networking
Reporter | ||
Comment 2•17 years ago
|
||
I dont believe this is the same, because if you look in the comments, he states that it is when he switches from wired to another wired, not wired to wifi (and that was my problem).
Comment 3•17 years ago
|
||
I think the changing of the IP address is what causes the bug, not which
media the underlying network uses.
Reporter | ||
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
I've seen similar behavior in Firefox 10, 11 and now 12. By contrast, an open Chrome browser does not hang.
In my work environment, I use wired Ethernet at my desk. When I stand up, I'm on wifi (a different network). At that point, Firefox freezes. I can vpn back into the wired network, Firefox is still frozen. If I reconnect to the wired network, Firefox un-freezes.
Reading the above comments, I see that the problem may be caused by the changing IP address. That's a possibility in my case.
In my case, the only work around is to kill the Firefox process and then restart.
Comment 5•13 years ago
|
||
Jice, thanks for the bugzilla comment.
can you comment with your OS information? That's probably relevant to the code in question..
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Whiteboard: [lame-network]
I've observed this running under Windows 7 (Enterprise edition, I believe).
Comment 8•11 years ago
|
||
I have long seen this behavior in Ubuntu. It continues to date -- currently Ubuntu 14.10, FF 34.0. It's quite disruptive whenever I need to go in either direction between ethernet and WiFi.
Comment 9•10 years ago
|
||
This happens to me every time I switch between wired and wireless network. The actual freeze happens when I click the bookmarks folder. The expanded list is blank. Firefox stops responding.
Comment 10•10 years ago
|
||
Recently upgraded firefox to latest version, since upgrading when switching networks(wired -> wireless on win7), firefox crashes and doesn't recover. I have to reboot to recover and continue to use Firefox. I get "Firefox is already running, but is not responding. The old firefox process must be closed to open a new window." Unable to kill the firefox process using task manager/manage processes.
Comment 11•10 years ago
|
||
this should be fixed with bagders new code
Status: REOPENED → RESOLVED
Closed: 17 years ago → 10 years ago
Resolution: --- → FIXED
Comment 12•8 years ago
|
||
I am on Firefox 52.0.2 (32-bit) on Windows 7 Enterprise (64-bit) and this has ALWAYS been an issue. In fact it just happened again a moment ago. As a previous poster indicated, this does not happen on Chrome.
You need to log in
before you can comment on or make changes to this bug.
Description
•