You can stop the script now, open the script in the debugger, or let the script continue.
You can stop the script now, open the script in the debugger, or let the script continue.ģ:14 PM A script on this page may be busy, or it may have stopped responding. This list is not as comprehensive list of the errors - I simply gave up trying to save all of the humongous number of URLs where this has happened.Ĭode: Select all A script on this page may be busy, or it may have stopped responding. The messages are delineated by lines of dashes. Please note that there are at least three chrome:browser URLs in this list. Here is a partial list of some of the URLs of the unresponsive scripts. This is NOT a problem associated with any particular site or sites. This occurs if I have only FF running or have other programs running - from 3 or 4 to 17. I've encountered the problem when running FF with2 or 3 tabs open and when I've got more, say 18 tabs open. This problem does not seem to be related to either the number of tabs open or the number of programs running. The other two computers are also at 38.0.5 from the prior releases - I installed that version after resetting the two computers to factory condition. I upgraded to 38.0.5 on my main computer (the CQ60, the one I'm using now) today. It has also occurred in FF 27(if not in earlier releases - I just can't pin down the start time) up to and including the current version - 38.0.5. I've had this problem in FF 3.6.24 -Yes, I know it is ancient, I was using it to test web pages for a bit of backward compatibility. Two of the computers were restored to factory condition in the past week and a half, one using the recovery partition and one using a set of restore discs from HP. I know what the script message means, FF thinks a script has stopped responding, such as a script in a endless or large loop.Īs I said, this is happening on three computers - the only ones I've been using for over a year. I'm saying that I right click on the text in the error message and it takes quite a long time for the context menu to be displayed.Īlmost always associated with this problem is FF "not responding," as indicated in the window title bar. More often than not, right clicking the text of the error message, in order to get the context menu to first "select all" and then "copy" will take anywhere from a few seconds to minutes. Sometimes closing the script will result in things running again right away and other time there are seconds to minutes between clicking Cancel and things running again. Closing the script will get the system running. FF will stop responding at all and FF will eventually report an unresponsive script. My computers will grind to a halt or to the point that other programs don't respond or take forever to do so. This is happening on three computers, I've detailed them below, search for "System Information" to find the information below. I can count on having some every time I use FF. Some time back - can't tell you exactly when this began - but I did post about it March 2015 and it had been happening for several months before that - I began encountering a huge number of unresponsive scripts.
I have spend hours and hours searching the forums and done Google searches galore and have found nothing which helps in the least bit.
Shockwave unresponsive script firefox how to#
If you have no problems in Safe Mode, you can safely assume it's one of your add-ons causing the error. If so, then you can enable that add-on again and try disabling another.Īnother option is to open Firefox in Safe Mode, which disables all add-ons.
To see what add-on may be causing a problem, you can disable an individual add-on and see if the error persists. Disable add-ons or run the browser in Safe Mode Each script or add-on error can differ in terms of what is displayed in the Browser Console, so there's not one specific thing we can recommend trying to find.
0 kommentar(er)
