Why do I keep getting the 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 s"?
I have 3 firefox windows with multiple tabs in each, but the main one (and sometimes others) freeze and preclude browsing showing a box saying "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://fctoolbar841468a1d7f44bd384e6bb0f13a06c64/content/fctoolbar.js:1" What stops the script? I gather it's not to do with Google Chrome but FF's internal template for web pages. So, an FF shortcoming, inability to cope, but with what? AFAIK, all software is up to date. I've restarted FF, restarted the laptop, but still the FF problem persists. What is causing it?
Ọ̀nà àbáyọ tí a yàn
This is most likely caused by a toolbar that is installed onto your version of Firefox. Most scripts that start with chrome:// are extensions.
I think that it is most likely the Nectar Search Toolbar that is causing the issue because it appears to be the only toolbar installed on your computer.
Try Firefox Safe Mode to see if the problem goes away. Firefox Safe Mode is a troubleshooting mode that turns off some settings, disables most add-ons (extensions and themes).
If Firefox is open, you can restart in Firefox Safe Mode from the Help menu:
- In Firefox 29.0 and above, click the menu button
, click Help 
and select Restart with Add-ons Disabled.
- In previous Firefox versions, click on the Firefox button at the top left of the Firefox window and click on Help (or click on Help in the Menu bar, if you don't have a Firefox button) then click on Restart with Add-ons Disabled.
If Firefox is not running, you can start Firefox in Safe Mode as follows:
- On Windows: Hold the Shift key when you open the Firefox desktop or Start menu shortcut.
- On Mac: Hold the option key while starting Firefox.
- On Linux: Quit Firefox, go to your Terminal and run firefox -safe-mode
(you may need to specify the Firefox installation path e.g. /usr/lib/firefox)
When the Firefox Safe Mode window appears, select "Start in Safe Mode".
If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article to find the cause.
To exit Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.
Ka ìdáhùn ni ìṣètò kíkà 👍 6All Replies (5)
Ọ̀nà àbáyọ Tí a Yàn
This is most likely caused by a toolbar that is installed onto your version of Firefox. Most scripts that start with chrome:// are extensions.
I think that it is most likely the Nectar Search Toolbar that is causing the issue because it appears to be the only toolbar installed on your computer.
Try Firefox Safe Mode to see if the problem goes away. Firefox Safe Mode is a troubleshooting mode that turns off some settings, disables most add-ons (extensions and themes).
If Firefox is open, you can restart in Firefox Safe Mode from the Help menu:
- In Firefox 29.0 and above, click the menu button , click Help and select Restart with Add-ons Disabled.
- In previous Firefox versions, click on the Firefox button at the top left of the Firefox window and click on Help (or click on Help in the Menu bar, if you don't have a Firefox button) then click on Restart with Add-ons Disabled.
If Firefox is not running, you can start Firefox in Safe Mode as follows:
- On Windows: Hold the Shift key when you open the Firefox desktop or Start menu shortcut.
- On Mac: Hold the option key while starting Firefox.
- On Linux: Quit Firefox, go to your Terminal and run firefox -safe-mode
(you may need to specify the Firefox installation path e.g. /usr/lib/firefox)
When the Firefox Safe Mode window appears, select "Start in Safe Mode".
If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article to find the cause.
To exit Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.
Seems to have worked. Emailed Nectar to advise them of their inadequate tool!
I am glad to hear that your problem has been resolved.
If you have not already, please mark this thread as solved by marking the solution.
This will help other users experiencing similar problems find help faster and more efficiently.
I hope you continue using our products and thank you for contacting Mozilla Support.
A variation on the theme: Having disabled the Nectar toolbar, when FF restarts (after computer restart) the main FF window has the Restore Session box, but on clicking Restart it soon comes up with box showing "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://browser/content/tabbrowser.xml:3035"
If not cleared, all the tabs show New Tab and would be lost if I don't restore a previous version of sessionstore.js Any ideas what's causing this inability of FF to restart transparently?
Now crashed and 2nd box has shown the message
Script: chrome://global/content/bindings/text.xml:31
Any ideas?