为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 2 个回答
  • 4 人有此问题
  • 2 次查看
  • 最后回复者为 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.

被采纳的解决方案

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 :-)

定位到答案原位置 👍 1

所有回复 (2)

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.

more options

选择的解决方案

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 :-)