"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: http://www.gstatic.com/news/js/2508309140-en-anchorman_main_jsmod.js:51"

When I go online with FF I get this error and for 30 seconds or so the page is dead as far a clicking on a link and so forth. My homepage is news.google.com and that is where this is happening. It only happens when first loading google. Not on any other page.

Have you tried setting your home page to google.com and seeing if you still get the error? This seems to be more on google's side...

Probably just a little bit of bad javascript code on the page. (Programmer made a typo or something...) I just visited Google news with Firefox 8 and no weird messages pop up. Wait a few days and see if it goes away (if it hasn't already). Otherwise you can download install NoScript and block the JavaScript on that site, but that is probably overreacting... Also, are you running the latest version of Firefox?

Thanks for the replies. As a matter of fact "news.google.com" is (was) my home page. 8.0 FF.

My homepage is mail.yahoo.com and I get this error randomly. For me, it causes FF to become completely unresponsive until the error dialog comes up.

Are you by any chance using any add-ons? I have tried replicating your issue, but no luck.

I have the same problem as "towheedm". And, yes, I have several add-ons. I have just moved my home page to something else. If I come back to Google News from another page I get the same unresponsive FF.

you might want to install 'add block plus' and 'no-script '

The error is exactly what it says on the tin. The page you accessed includes a bit of javascript code that's taking an unexpectedly long time to complete. It may even be stuck in a perpetual loop. So the browser gives you the choice to either terminate it or let it continue in the hopes that it will complete soon. If you terminate it the page should finish loading, but you may find some parts of it non-functional.

I believe there are some advanced settings in about:config that control the length of the timeout for this feature, and you can try blocking scripts entirely with noscript or similar, but in the end there's little else you can do. It's a bug in the page code and/or the javascript engine, and ultimately the fix has to be made there.

Thanks for all the replies. Mark this solved.

You mark your own thread as solved using the thread tools located at the top of the page.

Cheers!

Josh