Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

script DEBUGGER WON"T STOP RUNNING on ACCURADIO WEBSITE ONLY!!!!!!!!!!!

more options

The last question which is UNANSWERED is from 2 YEARS ago! So either I'm the first person in 2 YEARS to have this issue or everyone who had it deleted Firefox?

The last question which is UNANSWERED is from 2 YEARS ago! So either I'm the first person in 2 YEARS to have this issue or everyone who had it deleted Firefox?

All Replies (4)

more options

Hi AngieMe, could you give the full address of the page on http://www.accuradio.com/ where you have this problem. Or do all the stations you try have the same problem?

I noticed the site uses Flash. A common cause of unresponsive script errors is the protected mode feature of the Flash player plugin. That feature has security benefits, but seems to have serious compatibility issues on some systems.

You can try disabling it using the Add-ons page. Either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, find "Shockwave Flash" and click the More link. Then uncheck the box for "Enable Adobe Flash protected mode" and try that for a day to see whether it helps.

Any difference?

more options

I actually Uninstalled Flash from my computer a month ago so no that's not th problem and Script Debugger is the 1 problem i never had when it was Enabled/

more options

And its all the stations and Firefox Crashes on every website including this one.

more options

Sorry to hear about the crashes. If you are getting the Mozilla Crash Reporter form, your Firefox may have logged some data that would help track down the cause of the problem. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the last section of the support article "Firefox Crashes" for steps to get those crash report IDs from the about:crashes page, and then post some of the recent ones here.

Also and/or meanwhile, could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any less crashy?


I personally have not seen the script debugger open by itself. If that is happening to you, perhaps it would be best to disable it. You could try this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste devt and pause while the list is filtered

(3) Double-click the devtools.debugger.enabled preference to switch it from true to false

Does that make any difference?