Closed Bug 280997 Opened 20 years ago Closed 18 years ago

Autoconfiguration script hangs up Firefox process

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mk, Unassigned)

References

()

Details

Attachments

(1 file)

4.42 KB, application/x-ns-proxy-autoconfig
Details
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050203 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050203 Firefox/1.0+

Use of http://garmtech.lv/proxy.pac autoconfiguration script makes my Firefox
hang up if address isn't resolvable at all (for example www.asdas.asd).

Reproducible: Always

Steps to Reproduce:
1. Autoconfigure http://garmtech.lv/proxy.pac as autoconfiguration script
2. Visit any unresolveable hostname.

Actual Results:  
Mozilla stops responding. Can be only closed by Task Manager.

Expected Results:  
Show "Host not found" page.

The same error on: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.7.5)
Gecko/20041108 Firefox/1.0 (with ru-RU interface build).
Attached file Autoconfiguration file
This's original proxy autoconfiguration script.
Severity: major → critical
I blame this problem with Firefox freezing when configured with automatic proxy
discovery with Google Accelerator. It happened with Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050803 Firefox/1.0+, but also with
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050801
Firefox/1.0+ after I returned to the previous version.
There are about 60 users suffering from this bug in our corporate network. :-\

I digged a little for the reason of the problem and found that
 * this bug affects only Windows platform
 * when browser hangs, machine sends broadcast packets to the network trying to resolve the (non-existent) hostname over NetBIOS!

 I tried to reproduce the bug on Windows XP and Windows Server 2003, using two
browsers I had installed at the moment of testing: 
 1. Mozilla/5.0 (Windows; U; Windows NT 5.2; ru; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
 2. Mozilla/5.0 (Windows; U; Windows NT 5.2; ru-RU; rv:1.6) Gecko/20040407

 -- both browsers hangs on both OSes when trying to load a page that have an unresolvalble hostname in URL.

The browser quits hung state once it can resolve the name. I tried to
add a record to %systemroot%\system32\drivers\etc\hosts that maps bad hostname caused browser to hang to any IP, 127.0.0.1 for example, and browser immediately unlocks.

Our proxy autoconfiguration script is at http://www.hansa.kiev.ua/proxy.pac (it's long automatically generated using a list of network prefixes script very similar to the one that is attached by reporter)

P.S. I didn't install any third party browser *extensions* before testing, just browser itself and nothing more
Is this bug still reproducable? Please upgrade to a newer version of Firefox, preferably a nightly testing build available at http://www.mozilla.org/developer and report back with your results. Thank you.
Tested on "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7". As for me bug has been resolved (tested with attached file).

---cut---
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET http://www.garmtech-has-no-other-domains-than.lv/.

Reason: DNS lookup failure for: www.garmtech-has-no-other-domains-than.lv
---cut---
Assignee: bross2 → nobody
Since this bug now works for the reporter, I'm going to resolve it as "works for me". If you see this issue again using Firefox 2.0.0.3 or later, please file a new bug with steps to reproduce and a reference to this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: