We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Which variable in about:config rules whether the running timeout notification for Javascripts will be popped on screen?

  • 2 odgovora
  • 4 imajo to težavo
  • 2 ogleda
  • Zadnji odgovor od icos

icos
icos
more options

Hello there,

Sometimes i run some scripts where it might be happen that they hang up in an endless loop. At default there will pop on screen at a distinct time a message which asks for either aborting the page loading or continuing. There was also a check box (or button) for suppressing further such messages. Unfortunately I had disabled notification by this message, and now I have no way for interrupting a javaScript which is hanging in a endless loop.

Which variable in about:config rules whether the running timeout notification for Javascripts will be popped on screen?

Thanks for responding.

Hello there, Sometimes i run some scripts where it might be happen that they hang up in an endless loop. At default there will pop on screen at a distinct time a message which asks for either aborting the page loading or continuing. There was also a check box (or button) for suppressing further such messages. Unfortunately I had disabled notification by this message, and now I have no way for interrupting a javaScript which is hanging in a endless loop. Which variable in about:config rules whether the running timeout notification for Javascripts will be popped on screen? Thanks for responding.

Izbrana rešitev

Thanks jscher, It was - as you expected - due variable dom.max_script_run_time which value was 0 instead default 10 in my about:config. I've set this back to a non-zero value, and now all it's working fine :-)

Preberite ta odgovor v kontekstu 👍 1

Vsi odgovori (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

I do not see any setting along the lines you're describing in about:config, only the general dom.max_script_run_time setting which is set to 10 seconds by default.

I'm not sure the exception you made for the one site is stored across sessions. Does the problem recur if you exit Firefox and start it up again?

If so, hmm, it would be useful to encounter an examples that doesn't completely hang Firefox to test and explore which file might have that setting.

In the absence of a specific data source, you can flush ALL data about the site using the "Forget about this site" feature. It's pretty extreme: it removes site preferences, cookies, history, and bookmarks for the site. So that probably would be a last resort.

icos
icos Lastnik vprašanja
more options

Izbrana rešitev

Thanks jscher, It was - as you expected - due variable dom.max_script_run_time which value was 0 instead default 10 in my about:config. I've set this back to a non-zero value, and now all it's working fine :-)