Closed Bug 231472 Opened 22 years ago Closed 20 years ago

browser (and windows) hangs if a dialup connection drops while loading a page

Categories

(Core :: Networking, defect)

x86
Other
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: tomman, Assigned: darin.moz)

References

Details

(Keywords: helpwanted)

User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; es-ES; rv:1.6b) Gecko/20031208 Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; es-ES; rv:1.6b) Gecko/20031208 I am a dial-up user, and i've noticed in Mozilla 1.6b that if i am loading a page, and then i lost my connection, browser freezes, And, worse even, Windows freeses, so i need to reboot my PC. I've noticed this fail at least three times. Reproducible: Always Steps to Reproduce: 1.Run Browser with a dial-up connection 2.Load a page, then wait until the modem lost the connection while loading page (this may take a looooong while...) Actual Results: Browser and Windows freezes, forcing a hard reboot. Also some cache contents may be lost. Expected Results: Simply display an error message. I'm using Windows ME (Spanish), Mozilla 1.6b, latest Spanish translation, ChatZilla 0.9.56, Calendar 20030926, and for some strange reason, Talkback does not work (i've installed it).
Whiteboard: DUPEME
wow!i posted this 8 months ago and still no answer! It still happens, if anyone is interested.
Product: Browser → Seamonkey
*** Bug 280545 has been marked as a duplicate of this bug. ***
Assignee: general → darin
Component: General → Networking
Product: Mozilla Application Suite → Core
QA Contact: general → benc
Keywords: helpwanted
is there a short time between "lost my connection" and "browser freezes" ? Is there a differenece if you open "about:config" (as URL), enter "audodial" and change the option "network.autodial-helper.enabled" to "false" ?
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: 20 years ago
Resolution: --- → EXPIRED
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.