Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Dealing with unresponsive scripts?

  • 2 Antworten
  • 41 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von sm115498

sm115498
sm115498
more options

FF 35.0.1, no plugins active, no add-ons installed, Mac OS X 10.6.8

Hi, Every time I browse newegg.com (different accounts/boot drives), at least one open tab will soon spinning-beach-ball hang with message:

Warning: Unresponsive script

A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: http://cdn.krxd.net /ctjs/controltag.js.0663le6b152733188c0cac5a80502b56:2

[ ] Don't ask me again (Debug script) (Stop script) (Continue)

The only way I've been able to *sometimes* close the tab, is - if able - choose (Debug script), wait until debug window section fill in, then hit the close "x" on the right side of the tab, wait for the tab to close, and then for the same error message to reappear, then hit any of the choices to finish the closure. Otherwise Force Quit.

Thanks for any comment.

FF 35.0.1, no plugins active, no add-ons installed, Mac OS X 10.6.8 Hi, Every time I browse newegg.com (different accounts/boot drives), at least one open tab will soon spinning-beach-ball hang with message: Warning: Unresponsive script A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://cdn.krxd.net /ctjs/controltag.js.0663le6b152733188c0cac5a80502b56:2 [ ] Don't ask me again (Debug script) (Stop script) (Continue) The only way I've been able to *sometimes* close the tab, is - if able - choose (Debug script), wait until debug window section fill in, then hit the close "x" on the right side of the tab, wait for the tab to close, and then for the same error message to reappear, then hit any of the choices to finish the closure. Otherwise Force Quit. Thanks for any comment.

Alle Antworten (2)

guigs
guigs
more options

Hi sm115498, Does this script originate from the page that you were visiting? If not, please troubleshoot your extensions as well as Troubleshoot Firefox issues caused by malware

There is an old issue with not being able to prettify js scripts on sites and this was mentioned script. Does this happen on other computers, and does this happen after you clear the cache of the site from about:permissions?

sm115498
sm115498 Fragesteller
more options

Thanks for the reply.

Mainly I was trying to find out if there was a "stronger" way to get out of such a hanging/unresponsive tab without a Force Quit of the entire application - for future reference.

To me it looks like the script is associated with custom ads located along the side of the page, or tracking. I suspect that script is run only when certain ads are pushed to the page. (cdn.krxd.net is apparently part of Krux "Consumer Web Data Management".)

If further detail might assist: As stated above I run no extensions or add-ons (and generally either run as private browsing, or clear *everything* at least at the end of every session). Malware is not an issue, and the problem was repeatable on various accounts and boot volumes.

The newegg website is useless with javascript disabled, so that is not an option. I'd rather not start using add-ons, but it appears that there are some "JavaScript blacklist" ones out there. I suspect that the problem will probably disappear unexpectedly when the ad run expires or the script changes.