From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 BuildID: 1.0RC3 2002052306 following a link to a non existing newserver/message makes mozilla go wild (100% cpu usage, mouse pointer flickering) leaving nothing else than to kill mozilla program. Reproducible: Always Steps to Reproduce: 1. Open browser window 2. click URL Actual Results: 100% cpu usage, mozilla does not repond anymore Expected Results: some kind of error message I encountered this when clickin on a link on the mozilla 1.0 branch thinderbox page. (link to Branch Checkin Policy: news://news.mozilla.org:119/3CF50AF3.email@example.com news.mozilla.org is not reachable on my machine. But URL above shows same problem. (doesnotexist.mozilla.org)
Assignee: Matti → sspitzer
Component: Browser-General → Networking: News
Product: Browser → MailNews
QA Contact: imajes-qa → stephend
Dont' know what to tell you - this worksforme with build 6-5-2002 on Windows 2000. All I get is a quick JS alert that says, 'doesnotexist.mozilla.org could not be found. Please check the name and try again.'
Retried at home (different PC, also win2000) This time with Mozilla v1.0 ID:2002053012 I am seeing the same bug. Clicking the URL -> 100 % cpu usage. (after some trying, It is possible to get the back button to work, then cpu usage goes normal again. You cannot do anything than trying (hard) to press back) But you're not seeing this ? Weird.
Are you on dialup or broadband? Any proxy servers in the way? It could be something in the networking code, which is failing to pass back some event saying 'domain not found' in the correct time.
I'm seeing this both at work and at home. home: dialin, no proxy server work: company network, proxy server
I don't know what changed but... this seems to work now (mozilla 1.2a on windows 2000) steps: 1) click url result: error box is shown (as expected) I think the bug can be closed
Thanks, harm. Marking worksforme based on reporter's comments.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
verified, per reporter's comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.