Closed Bug 229961 Opened 16 years ago Closed 13 years ago
Browser hangs if wireless connection is lost temporarily
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 When using a wireless connection both Mozilla 1.5 and Netscape 7.1 will "hang" if the connection is lost temporarily. It is still possible to close any open Browser windows, but links etc. will not be followed. If all browser windows are closed and Mozilla is restarted from scratch, a message appears that the previously used profile is still in use. This message also appears if Mozilla is started from the memory-resident toolbar icon. The workaround is to kill the Mozilla process using the task manager and restart. This solves all problems until the next loss of connection. Reproducible: Always Steps to Reproduce: Steps to reproduce 1. Start Mozilla 2. Surf to Google 3. Interrupt wireless connection 4. Enter search in Google The problem is reproducible on the following two systems: Fujitsu-Siemens Xpert (Athlon XP 1700+), 256 MB, Draytek Vigor 510 IEEE 802.11b WLAN USB OS: XP Home Edition Version 5.1.2600 (German) and Toshiba Tecra 9100, Pentium 4 Mobile CPU 1,7 GHz, onboard IEEE 802.11b WLAN OS: Microsoft Windows XP Professional Version 5.1.2600 Service Pack 1.0 (German) Router: Draytek Vigor 2500 ADSL Router The problem is reproducible with the following browsers: Netscape 7.1 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Actual Results: No results appear No Talkback appears Expected Results: Displayed the search results from Google
Your build is too old to report bugs on. Can you reproduce this with a nightly?
Looking at your steps, I would like to know if mozilla is running in the task manager after you close all the windows, before you try to launch it again. Also, please see if "Quick Launch" is on in your Prefs.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
*** This bug has been marked as a duplicate of 213637 ***
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.