[Webkit-unassigned] [Bug 6998] New: Very poor performance of setTimeout function
bugzilla-daemon at opendarwin.org
bugzilla-daemon at opendarwin.org
Wed Feb 1 01:51:31 PST 2006
http://bugzilla.opendarwin.org/show_bug.cgi?id=6998
Summary: Very poor performance of setTimeout function
Product: WebKit
Version: 420+ (nightly)
Platform: Macintosh
OS/Version: Windows XP
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: JavaScript
AssignedTo: webkit-unassigned at opendarwin.org
ReportedBy: sjoerd at backbase.com
The following code shows a simple loop which uses the setTimeout function to
call the same function again, but without the performance drain of a
while(true) loop.
function testTimeout() {
setTimeout(testTimeout,0);
}
This works perfectly in Internet Explorer, Firefox and Opera. Taking almost 0%
CPU-time. But Safari / Webkit takes 100% of CPU-time... This is a very serious
performance problem. With setTimeout on 1 ms, it takes 25% which is still
unacceptable.
--
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list