Closed Bug 81270 Opened 23 years ago Closed 23 years ago

mozilla hangs/crashes on invalid domain names

Categories

(Core :: Networking: HTTP, defect)

defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 81273

People

(Reporter: f300v10, Assigned: neeti)

References

()

Details

(Keywords: crash, dataloss, hang)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; rv:0.9+) Gecko/20010516 BuildID: 2001051608 Any invalid domain name causes mozilla to hang/crash Reproducible: Always Steps to Reproduce: 1.type in an invalid domain name 2. 3. Actual Results: mozilla hangs Expected Results: Should report the domain name was not found This is a recent regression.
Verified on Windows NT build 2001051604, setting OS to all
OS: Linux → All
using build #2001051604 on Win2k (SP2) The same thing seems to happen when you enter a search term. For intance, puting "spam" into the URL field and hitting enter should take you to a search page and search for the term "spam" for you. Mozilla used to do that, at least. now, it hangs just like junk.junk.com does. Actually, I waited for about 30 seconds to 1 minute watching Mozilla be hung, then it crashed. Talkback ID: #TB30534799Z Jake
Keywords: crash, hang
it hangs then crash when it can't contact a domain - valid or invalid. Confirming. I see this at http://www.kde.org today - it's down right now seemingly. NC4.77 eventually spawns an error message "the server could be down or is not responding" - mozilla freezes, using lots of CPU untill it crashes several minutes later.
Status: UNCONFIRMED → NEW
Ever confirmed: true
beta stopper. bringing over info from bug 81335
*** Bug 81335 has been marked as a duplicate of this bug. ***
Hardware: PC → All
81273 has a patch attached - marking this as a dupe. *** This bug has been marked as a duplicate of 81273 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
qa to me. VERIFIED: dupe b/c it is a url failure.
Status: RESOLVED → VERIFIED
QA Contact: tever → benc
You need to log in before you can comment on or make changes to this bug.