> My Home Page URL: http://preview.my.earthlink.net"

> Error Message: "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: Chrome://xcm/content/xcm/overlay.js 196

> Could someone explain this to me? Is it a FF 3.0 bug? I am not that familiar with chrome or scripts. Is there a fix or work
> around?

>> My Home Page URL: http://preview.my.earthlink.net"

>> Error Message: "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: Chrome://xcm/content/xcm/overlay.js 196

>> Could someone explain this to me? Is it a FF 3.0 bug? I am not that
>> familiar with chrome or scripts. Is there a fix or work around?

> Hi Brian,
> Choosing a complicated  home page is probably not a good idea, but  it
> is a lot better than choosing  a default  Google page that some choose
> despite the built-in  search box.   It's obviously good at telling you
> that you
> have a problem.

> Have you checked the following,  you are not likely to find that message
> but you may find some of your extensions have or have had problems in
> the past.
>     http://kb.mozillazine.org/Problematic_extensions
> If you have AVG Anti-virus you  probably also have  "AVG Safe Search" so
> check your add-ons even if you aren't aware of installing it.

> I would disable all themes  before investigating to make sure you still
> have
> problem and leave the off until solved.

> The best  thing to test  first  is if you have a problem with your site
> with a new
> profile that has none of the changes that you make (get rid of "ABV Safe
> Search"
> if you have it, shows up even in a new  profile).

> Check the box at the top of my web page with the  red dashes around it,
> some
> have been fixed since but  I  had to  disable or remove over 20
> extensions that
> interfered with  2.0.0.14 or Fx3.    It only takes one.    Here is a
> list of some that
> I still have disabled meaning may still have problems or weren't worth  
> effort
> to investigate.
>  /Find Bar/,

> Unresponsive Script, and whiteouts.  Some  I've disabled in 2.0.0.14 (*
> disabled on 2008-02-08): /Find Bar/,   * [Autocomplete Manager], *
> EditCSS, * Extended Cookie Manager, * InspectThis, [PermaTabs],
> Professor X,  RealPlayer Browser Record Plugin, * [searchcache],  *
> SnagIt Firefox Extension (application works fine don't need/use the
> extension)     addition notes scattered through my home page.

> Script Busy   (#scriptbusy)

>    Something to test after adding/enabling an Extension: Ctrl+A (select
> all) followed by right-click to bring up context menu.  Big problem if
> instead of context menu you get "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 [Stop Script] [Continue]".  
> These extensions are a problem: and have been disabled/uninstalled:  
> Line Marker (200607), Quick Sum (0.1), Translate (0.6.0.9), gTranslate
> (0.3.1).  Also as you approach Firefox 2.0.0.12 some extensions that get
> (not responding) and similar errors.

> You can up the timeouts but it isn't likely to help,  these
> numbers below are exceptionally high.
>    dom.max_chrome_script_run_time       integer  180
>    dom.max_script_run_time                      integer  180

> Then if the simpler means fail,  there's the disabling of  half of the
> active extensions until the problem is solved then re-enable half of
> the disabled extensions at a time, rather than all at once.   (binary
> testing)
> I hate this even though the time is often quicker than trying to guess
> which ones are bad -- hate it because I always have some extensions
> disabled and if I turn a bad one back on, I've got another problem.