Firefox-arrrgghhhhh!!
April 20, 2006 10:40 AM   Subscribe

Every few minutes or so my Firefox browser freezes up (which freezes up my entire system) and I get an error box eventually that says "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." Then it gives me an option to "stop script" or "continue". I am tired of doing this every few minutes or so. Please help.
posted by sandra194 to Computers & Internet (18 answers total) 1 user marked this as a favorite
 
This usually means javascript is caught in an infinite loop on some webpage. Does this happen on any specific site?
posted by null terminated at 10:48 AM on April 20, 2006


I get the same message for very long pages which use javascript, if that helps.

Does it happen when just staying on simple pages (like going through Google search results)?

Also, to help us help you, posting what extensions you have installed in FF would be good.
posted by Kickstart70 at 10:49 AM on April 20, 2006


Also, what version and OS are you using?
posted by nitsuj at 10:51 AM on April 20, 2006


This started happening to me all the time too. I googled and found this but haven't done it yet.
posted by CunningLinguist at 10:53 AM on April 20, 2006


Response by poster: well, it happens when FF is just sitting there open to my chosen homepage--which is Netvibes
posted by sandra194 at 10:55 AM on April 20, 2006


Response by poster: oh, I am using Windows XP
posted by sandra194 at 10:56 AM on April 20, 2006


Response by poster: and I am using the most recent version of FF--but this has been happening for awhile
posted by sandra194 at 10:57 AM on April 20, 2006


Netvibes is very JavaScript-heavy. An easy solution is to change to another homepage (e.g. ProtoPage).

If you're running GreaseMonkey, check if there are any scripts running when Firefox hangs.

If you're determined to find out specifically what is causing the script to run slowly, the Venkman debugger for Firefox might help (it's distinctly non-trivial, though).
posted by matthewr at 11:05 AM on April 20, 2006


I used CunningLinguist's hack. It helped alot.
posted by AwkwardPause at 11:06 AM on April 20, 2006


I kept getting the same errors over at textamerica.com and audioblog.com. I tried the hack and (so far) it's working. NICE!!!
posted by damnjezebel at 11:07 AM on April 20, 2006


Doesn't CunningLinguist's hack just cause Firefox and Windows to hang for longer before the slow script popup appears?
posted by matthewr at 11:09 AM on April 20, 2006


Response by poster: and come to think of it, i don't get this message on my home computer--just on my work computer, of course that could mean anything --or nothing--(oh my head hurts)
posted by sandra194 at 11:13 AM on April 20, 2006


My link to ProtoPage was broken - it missed off the '.com'. But, when I clicked on it, Firefox automagically guessed that I wanted to go to www.protopage.com. It seems to guess based on your browsing history, so if you try 'www.bbc', it'll go to www.bbc.co.uk, but if you type 'www.cam', it'll go to www.cam.ac.uk. What a great, hidden-away Firefox feature!
posted by matthewr at 11:17 AM on April 20, 2006


Have you tried disabling all your extentions?
posted by kc0dxh at 11:53 AM on April 20, 2006


actually, matthewr, you are getting the google "i'm feeling lucky" results for 'www.bbc' and 'www.cam', which is firefox's default action for unrecognized stuff in the location bar
posted by misterbrandt at 12:04 PM on April 20, 2006


Ah! Thanks misterbrandt.
posted by matthewr at 1:02 PM on April 20, 2006


Response by poster: well..I don't want to disable my extenstions because I want to use the ones that I have
posted by sandra194 at 6:37 PM on April 20, 2006


I had the same problem awhile back; it turned out to be the "SessionSaver" extension I was running. Replaced it with "Tab Browser Mix" (which also has session saver functionality), and the problem was solved. As a bonus, FireFox as a whole ran much faster.

Of course you want to keep your extensions, but turning them all off and seeing if the problem goes away, and (assuming it does) turning them back on a few at a time until you come to one that causes the problem to return can help identify one that needs to be upgraded or replaced with another that provides similar functionality...
posted by nonliteral at 8:38 PM on April 20, 2006


« Older Desert winds, the call to prayer and a mysterious...   |   A Legend in the Making Newer »
This thread is closed to new comments.