MozillaZine

Dom.max chrome script run time

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is dom.max_chrome_script_run_time.

This article describes the preference dom.max_chrome_script_run_time. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

Contents

[edit]

Background

JavaScript that takes a long time to run can make the browser unresponsive. As such, a check is built in to allow long-running scripts to be aborted. That check is now able to differentiate between scripts running in web pages (content) and scripts running in the application’s chrome. This preference determines how long scripts running from chrome are allowed to run before the user can choose to abort the script.

[edit]

Possible values and their effects

The value is a positive integer, determining the number of seconds of execution (wall time). 0 and negative values are considered “forever.” Default value is 20.

For Thunderbird and SeaMonkey on Mac, the default is 0 since 2012-08-21 trunk build (bug 482811).

[edit]

Caveats

  • This preference only controls scripts running with chrome privileges. For scripts with content privileges, see dom.max_script_run_time.
[edit]

First checked in

2006-07-27 by Johnny Stenback

[edit]

Has an effect in

  • Mozilla Firefox (nightly builds after 2006-07-27; 2.0)
  • Thunderbird (nightly builds after 2006-07-27; 2.0)
  • SeaMonkey (nightly builds after 2006-07-27; 1.1)
[edit]

Related bugs

[edit]

Related preferences

Retrieved from "https://kb.mozillazine.org:80/Dom.max_chrome_script_run_time"