Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Unresponsive script error without changing script?

  • 4 отговора
  • 1 има този проблем
  • 12 изгледи
  • Последен отговор от pellky

more options

All of a sudden all of my websites that run the same slideshow script (Flash/XML, with image links) now get this error when clicking on one of the slideshow images to go to a specified page:

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: http://accessretirement.com/new/:16

(all slideshow instances are showing the same :16 at the end of the URL, this is just one example)


Clicking on the link DOES take you to the new page about the same time the error window pops up. This is happening on an iMac running 10.8.4 and a laptop running Windows 7 Home Premium. This error does not happen in Safari. It works just like it's supposed to.

Really appreciate any thoughts, regular IT guy is out and I am not a developer. :-)

All of a sudden all of my websites that run the same slideshow script (Flash/XML, with image links) now get this error when clicking on one of the slideshow images to go to a specified page: 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: http://accessretirement.com/new/:16 (all slideshow instances are showing the same :16 at the end of the URL, this is just one example) ----- Clicking on the link DOES take you to the new page about the same time the error window pops up. This is happening on an iMac running 10.8.4 and a laptop running Windows 7 Home Premium. This error does not happen in Safari. It works just like it's supposed to. Really appreciate any thoughts, regular IT guy is out and I am not a developer. :-)

Всички отговори (4)

more options

I tried it without the :16 on Windows 7 (the :16 led to a page not found error).

I find there is a long delay after clicking the Flash image before the next page loads, but no error message. I have made some modifications to my Flash configuration, so that could explain part of the difference on Windows 7, not sure about Mac.

(1) Disabled hardware graphics acceleration in Firefox and in Flash

(A) In Firefox, un-checked the box here and restart:

orange Firefox button (or Tools menu) > Options > Advanced > General > "Use hardware acceleration when available"

(B) In Flash, used this support article from Adobe: http://helpx.adobe.com/flash-player/kb/video-playback-issues.html#main_Solve_video_playback_issues

(2) Disabled protected mode (Windows Vista/7/8)

Used this support article from Adobe under the heading "Last Resort": Adobe Forums: How do I troubleshoot Flash Player's protected mode for Firefox?

more options

I appreciate your reply, but the issue is in clicking on the image link (which generates the unresponsive script error), not in the slideshow simply looping (which does not generate the error message).

more options

Hi pellky, if I understand correctly, each of the 3 images in the slide show leads to a different page. Those "links" worked for me, but there was a long delay in loading the pages. There was no outward indication of the reason for the slowness, but it could have something to do with a script. Not sure. Not a Flash developer.

more options

Your understand is correct, and yes there is a delay as well as an error message on both Windows and Mac. There is neither a delay nor an error message using Safari. Problem seemed to start with the last Firefox update.