[Webkit-unassigned] [Bug 92009] Stop using currentTime()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=92009





--- Comment #4 from Yong Li <yoli at rim.com>  2012-07-27 15:07:56 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > But the problem is still there: what if user adjusts system date to 1 month earlier?
> 
> A good way to make further use of this insight is to do some testing. We can find out how real these problems are that could happen when the user changes the computer time.
> 
> We are experts so we can see the bugs that could exist, but testing makes them more concrete and helps motivate us better than just architectural insight.

I've seen changing system date back when Safari win32 is loading a page (like cnn.com, bgr.com) caused the page frozen (cannot be scrolled) for a while (>20 seconds). Not sure if it is related to this issue. Such kind of issues usually take developers quite some time to finally realize it is timer that doesn't work.

One way to show real problems might be running a script that keeps changing system date on a testbot at same time when it is running layout tests. But bugs like BlockFreeingThread never wakes up or takes very long to wake up are very hard to be detected.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.