Closed Bug 450153 Opened 16 years ago Closed 16 years ago

Firefox doesn't react after wrong URL

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
2.0 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 235853

People

(Reporter: simonhanisch, Unassigned)

References

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 If I have typed an uncomplete or wrong URL like "web.d" or "t-mobilde.de", which have a non-existing top- or sublevel domain, Firefox doesn't react to user actions for a very long time (forever?). Reproducible: Always Steps to Reproduce: 1. type web.d 2. wait... 3.
The reason Firefox is taking a long time is that it is looking up the website address, and upon not finding it, looking in more places (in easy terms). Does FF eventually show a Page Load Error page? If not, then we have a bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Yes, FF shows a Page Load Error page - but after several minutes (2-4). During this time FF doesn't react to user actions. So I'm not able to correct my wrong URL. The only possibility to use it anyway is to kill FF by task manager and start it again. P.S.: The internet explorer has a similar behavior - but who want to be like the IE! ;-)
So you get a hang when FF is looking up the address, correct?
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Whiteboard: [hang?]
Yes, I get a hang when FF is looking up the (non-existing) address.
Severity: normal → critical
Keywords: hang
Whiteboard: [hang?]
Version: unspecified → 2.0 Branch
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 MS Win XP Pro v.2002: SP2 I was unable to reproduce this. Steps Taken: -Entered web.d in address bar. -While FF was trying to locate the page and before the Page Load Error, I typed in another non-existing URL asks.d. -FF produced a Page Load Error for both urls. -Entered web.d again -Entered existing URL in address bar. sprint.com -FF navigated to Sprint.com
At the moment it works at my PC too, for FF and Internet Explorer. But in my office it doesn't work for both. When I have inserted the bug it haven't worked, at home and at office. In my office I am probably behind a proxy. So I suppose that this hang is caused by the constellation of the environment/network and the interactions of FF. But under this circumstances it think that it is almost impossibly for you to solve this problem.
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 I have the same here in my company with a proxy. Firefox freezes for approx. 6-7 seconds without any response. CPU and memory usage is normal over all the time. Maybe FF is waiting for a mutex or event? I'm using an auto-proxy-configuration (PAC). Maybe this is a dupe of bug 235853
Depends on: 235853
Do the changes from bug 208312 not help this case? Do they exacerbate the problem?
I doubt 208312 will bear on the issue - it looks like the reporters are using proxies in which case the FF DNS cache and resolver isn't used other than in reaching the proxy itself. sounds like we need to figure out what is blocking during the timeout in the proxy case, which doesn't otherwise block.
Ok, then this is probably just a dupe of bug 235853.
No reply, so assuming dupe of bug 235853.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.