User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Beginning with version 1.0.6, Firefox crashes on startup when either "Auto-detect proxy settings for this network" or "Automatic proxy configuration URL" are selected. ie: user_pref("network.proxy.type", 2); or user_pref("network.proxy.type", 4); Reproducible: Always Steps to Reproduce: Starting with either a working 1.0.5, or an entirely clean Firefox profile..: 1. Click Firefox > Preferences > General > Connection Settings 2. Choose "Auto-detect proxy settings for this network" 3. Click OK 4. Restart the browser At step 2, the issue can also be invoked by using the "Automatic proxy configuration URL". If you skip step 4 (browser restart) and simply start browsing, Firefox crashes then also. Actual Results: Firefox crashes before fully starting up, and Talkback is invoked (Talkback doesn't work behind an authenticated proxy anyway...). Expected Results: Firefox launches correctly. Downgrading back to Firefox 1.0.5 seems to resolve the issue. Manually setting proxy server information ("Manual proxy configuration") allows Firefox 1.0.6 to operate correctly. Mac OS X 10.4.2

The attached log records two crashes caused by this issue.

One co-worker indicated this also occurs to him with Firefox 1.0.6 for Windows (XP), and another indicated he's experienced the same thing with Mozilla (suite) 1.7.10 on Mac. In both cases, the problem could be worked around by using the manual proxy configuration option. The issue kicks in as soon as the browser tries to load an external URL, eg: the default Firefox homepage, that requires the proxy (ie: it's not a launch issue per-se).

Crash also occurs on Mozilla 1.7.11.

does this happen on trunk? and can you crash w/ talkback, i'd really appreciate line numbers. bug 302100 is currently fixed on trunk only, but as i can't figure out where in http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/caps/src/nsScriptSecurityManager.cpp&rev=1.229.6.6.2.10&mark=3441-3479#3440 you'd crash, i'm having a hard time figuring out what to do.

Have done a crash with the release version of Mozilla 1.7.11 and submitted through Talkback (I would have before, but Talkback doesn't support authenticated proxies, so I had to workaround this). Also downloaded the Mac version from: ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ which appears to be 2005070211, and this doesn't exhibit the crash, although it would also appear to be a month old. And downloaded the Mac version from: ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2005-08-02-06-1.7/ (20050802), which does crash. Have also submitted this through Talkback.

if you run components/talkback.app you should see incident 8041558 which corresponds to nsJSPrincipalsSubsume() sent 2005-08-02 19:49:30.0 MozillaOrgMozilla17MacOSX2005072723 which makes this crash a duplicate of bug 302100 as i suggested in comment 4. sorry, mozilla renamed itself to seamonkey, current builds are at: try http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ it should not crash either. please confirm so that i can resolve this bug. i'm not sure whether we'll be able to get the fix into 1.7.x, i have asked for approval.

Confirmed, SeaMonkey 1.0a (2005080210) does not crash with either auto-detected (DHCP) or auto-configured (PAC) proxies.

*** This bug has been marked as a duplicate of 302100 ***