[Webkit-unassigned] [Bug 27149] New: JavaScript runaway script dialog.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jul 10 06:22:57 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=27149
Summary: JavaScript runaway script dialog.
Product: WebKit
Version: 525.x (Safari 3.2)
Platform: Macintosh
URL: http://trac.webkit.org/browser/trunk/WebCore/bindings/
js/kjs_binding.cpp?rev=14904#L69
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: mrithulashan at gmail.com
One of the programming barriers that we web developers are constantly bumping
up against is the dreaded long-running script dialog (the runaway script
dialog). These dialogs are displayed whenever the JavaScript code takes too
long to execute. Safari does not determine slow script by total amount of
statements the engine has executed. Looks like Safari uses script execution
time (5 seconds to be exact) to determine if a a script is slow:
http://trac.webkit.org/browser/trunk/WebCore/bindings/js/kjs_binding.cpp?rev=14904#L69
[ Line # 72 ]
Firefox determines that a script is long-running by timing how long the script
engine has been executing code continuously. The default time is set to 10
seconds and can be altered via about:config. [ Note that the amount of time
modal dialogs, such as alerts, are displayed does not count against the script
engine execution code]. When this execution time has been reached, Firefox
displays the 'unresponsive script' dialog.
In Safari > Sure there is the Disable Runaway JavaScript Timer under > the
Develop menu. But I have thousands of remote users for my application across
the country. Instead of using "script execution time" can it be "total amount
of statements the JavaScript engine has executed?" This should help application
developers who use 'applets' to load them with out the 'slow script' error.
Thanks.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list