[Webkit-unassigned] [Bug 6998] Very poor performance of setTimeout function

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=6998


ap at nypop.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at nypop.com




------- Comment #4 from ap at nypop.com  2006-02-01 05:58 -------
I'm wondering what the explanation of low processor usage in other browsers is
- actually, 100% processor usage looks like what is explicitly requested here
(similar to a while(true) loop). Probably I'm missing something.

BTW, Win32 timers wouldn't honor a timeout lower than a certain threshold
(normally, 10 ms). Maybe Firefox emulates this behavior?


-- 
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.