Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Archived

Getting "script on this page may be busy, or it may have stopped responding" error since upgrading to 4.0.1

asapReps replied
asapReps

Getting error when going to website since upgrading to 4.0.1: --- start 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: http://www.gogreenwingreen.com/js/jquery-1.5.2.min.js:16 --- end message ---

This ony happens on PCs that have 4.0.1 installed. I have a PC that has 3.1.6 and this error does not appear.

I am using 4 profiles and the error appears with all 4 profiles.

I copy the places.sqlite between the 4 profiles t kee the bookmarks consistent for all profiles.

Getting error when going to website since upgrading to 4.0.1: --- start 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: http://www.gogreenwingreen.com/js/jquery-1.5.2.min.js:16 --- end message --- This ony happens on PCs that have 4.0.1 installed. I have a PC that has 3.1.6 and this error does not appear. I am using 4 profiles and the error appears with all 4 profiles. I copy the places.sqlite between the 4 profiles t kee the bookmarks consistent for all profiles.

Modified by asapReps

All Replies (2)

Start Firefox in Use Troubleshoot Mode in Firefox to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

Ok, was on the web page and did Help > Restart with Add-ons disabled and got into safe mode. Java script error did not show up after entering the information, so I guess now it's time to disable add-ons and try and figure out which one might be causing the error to be produced.