590247 - Unresponsive script warnings shouldn't flag components/nsProxyAutoConfig.js:XXX

Status: RESOLVED DUPLICATE of bug 235853

(Core :: Networking, defect)

Description

[alex_mayorga]

User-Agent:       Mozilla/5.0 (Windows NT 6.0; rv:2.0b5pre) Gecko/20100824 Minefield/4.0b5pre
Build Identifier: Mozilla/5.0 (Windows NT 6.0; rv:2.0b5pre) Gecko/20100824 Minefield/4.0b5pre

Loading the URL Minefield becomes unresponsive for some seconds and then shows this message:
"Warning: Unresponsive script
A script on this page may be busy, or it may have stopped responding. You can
stop the script now, or you can continue to see if the script will complete.
Script: jar:file:///C:/Program
Files/firefox/omni.jar!/components/nsProxyAutoConfig.js:118"

This was initially reported at https://bugzilla.mozilla.org/show_bug.cgi?id=562406#c3

There it was suggested that http://hg.mozilla.org/releases/mozilla-2.0/file/09565753ce5f/netwerk/base/src/nsProxyAutoConfig.js#l117 "it's using sync APIs
(!), that's most likely a problem with the DNS server/client not
responding/resolving, i.e. a site problem. And nsProxyAutoConfig.js should use
dns.asyncResolve(), but that's also a different bug"

Reproducible: Always

Steps to Reproduce:
1. Go to URL
2. See error
Actual Results:  
"Warning: Unresponsive script" shows.

Expected Results:  
No warning or a more descriptive message.

Using "Automatic proxy configuration URL".

Comment 1

[alex_mayorga]

Got this again today loading www.thewildernessdowntown.com on Mozilla/5.0 (Windows NT 6.0; rv:2.0b5pre) Gecko/20100831 Firefox/4.0b5pre ID:20100831040721

Comment 2

[alex_mayorga]

Got the message on comment #1 and this new one when first loading http://azarask.in/projects/algorithm-ink/#b32debe8 with Mozilla/5.0 (Windows NT 6.0; rv:2.0b9pre) Gecko/20110106 Firefox/4.0b9pre ID:20110106030349

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: jar:file:///C:/Program Files/firefox/omni.jar!/components/nsProxyAutoConfig.js:126"

Comment 3

[alex_mayorga]

The message has changed on Mozilla/5.0 (Windows NT 6.0; rv:2.0b9pre) Gecko/20110109 Firefox/4.0b9pre ID:20110109030350 to:
"A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: resource://gre/components/nsProxyAutoConfig.js:126"

This might be related to a big proxy auto configuration (PAC) file.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to comment #3)
> This might be related to a big proxy auto configuration (PAC) file.

Does it go away if you startup (if you can) without the proxy?

Comment 5

[alex_mayorga]

(In reply to comment #4)
> Does it go away if you startup (if you can) without the proxy?

Can't remove the proxy unfortunately =(

I visited http://azarask.in/projects/algorithm-ink/#b32debe8 with Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:6.0a1) Gecko/20110524 Firefox/6.0a1 ID:20110524030216 today and now the messages have changed a bit, below is what I see:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: resource:///components/nsProxyAutoConfig.js:122

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: resource:///components/nsProxyAutoConfig.js:118

I believe the actual bug is that unresponsive script warnings shouldn't flag components/nsProxyAutoConfig.js at all, right?

Comment 6

[alex_mayorga]

Tried a second time, Nightly becomes "(Not Responding)" twice and displayed this other warning:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: resource:///components/nsProxyAutoConfig.js:1197