I have a message that references a script that is running too long and I cannot get it to go away. What can I do?
I am getting a message about this script: * see box below*
I cannot get the script to stop running. This problem just started this afternoon. It never clears up - even after 20 minutes or so. What can I do? I have uninstalled Firefox, rebooted and then reinstalled and the same thing happens. It just started today.
I am using a MAC - OS version 10.7.5
This is what the warning box says:
Warning: Unresponsive script
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: https://fbstatic-a.akamaihd.net/rsrc.php/v2/yd/r/8ojmoO5uTcS.js:5
I tried to paste the raw data from the troubleshooting information page, but it made this message too long ...
Gewysig op
All Replies (13)
Please create a screenshot of the problem you're seeing by following the guide mentioned at How do I create a screenshot of my problem?.
Once you've done this, attach the saved screenshot file to your forum post by clicking the Browse... button below the Post your reply box. This will help us to visualize the problem.
I changed my home screen from Facebook to the Mozilla search screen. the script does not start up until I go to Facebook.
1. This is the first screen. If I choose "cancel" it goes t my new home screen and the script does not start until I go to Facebook.
2. when I go to Facebook, this is where the beachball cursor starts (you can not see it on the screen shot), but there is a "connecting to" box in the lower left corner of the screen. After waiting, the warning box comes up.
3. Screen shot of warning box - the information in the lower left corner box has changed.
After this comes up, it does not matter if I click Stop or Continue, the beach ball comes back and I am stuck. Even if the beach ball goes away, the moment I click on the page or try to scroll, it starts back up again.
Does this help at all?
Thanks!
Yes very helpful actually. Please see the following:
Warning Unresponsive script - What it means and how to fix it
Post back with results.
Gewysig op
I tried starting Firefox in safe mode using the option of: in the help -> troubleshooting -> restart with add ons disabled...I selected the option of "start in safe mode". and then to
I still have the beach ball and the unresponsive script issue.....
You can see in the third shot that although Firefox is open, none of the items are showing on the menu bar (I hope that is the right name for it).
Should I reset firefox?
I didn't mention safe mode. However If the error happens only on a specific website, you can block scripts from running on that website. Many sites still function even if scripting is disabled.
- Install the YesScript extension and restart Firefox.
- On the menu bar, click the Tools menu and select Add-ons.
- In the dialog that comes up, click on the YesScript entry.
- Click Preferences.
- In the YesScript Blacklist dialog, type the URL of the site that's giving you problems in the text box.
- Click Add. The domain name of the site will be added to the list.
Now that the problematic site has been blocked from running scripts, it will no longer cause unresponsive script warnings.
Again go to the following support article which I have set to MAC OSX already & read up on the first 2 options.
I would try what I suggested above before doing complete reset which will wipe everything.
Warning Unresponsive script - What it means and how to fix it
Please select the appropriate response "Solved/Solution" to close out this thread & mark issue as solved if this has solved your issue. Thank You.
Gewysig op
Exit safe mode & restart FF normally & what I just suggested. Nothing is showing up as you pointed out on the third picture because FF when in safe mode disables all add-ons and extensions basically putting it into default the way it was if first downloaded without any previous versions etc...
Gewysig op
This is happening to me and just started after updating to the latest Firefox. This doesn't happen in Chrome nor does it happen in Safari.
I cannot get it to go away no matter what I do. I have to force quit FF - so I guess until someone recognizes this is an issue, I can no longer use FF.
blueoktober did you try the extension that I mentioned I previously mentioned? It sounds like you haven't in which case I would recommend giving that and my other suggestions a try first before attempting anything else further.
If you are having the same issue, please either start a new thread/question or select you are having this problem also so that you are included in the communication loop.
Gewysig op
I have the same problem. I read somewhere that if you use another browser and log out from the facebook chat it will help. I did so, and now I can use facebook.
This is more a temporarily fix I guess.
Hi, i just tried the solution given by Dbellca92, it's working, i can connect to my facebook account on Firefox 18, on my macbook pro / Mac OSX 10.6.8. But obviously i can't consult my real-time news on the right ticker, and i can't access to the chat function neither, so is it gonna be an update for the java system, or from facebook, or even a patch from you guys in Firefox ?
I also have this problem on the last version of Firefox (18) and a MacBook Pro 10.6.5.
Adding sites to a blacklist makes not difference. When I bring up facebook on Firefox later, another website takes the place of the other ones that were running non-responsive scripts.
How do I wipe everything?
If that does not work, I have to stop trying to use Firefox - this is simply too frustrating...I like the browser, but I can't take this...
Try to create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
- https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.