Closed
Bug 1171443
Opened 9 years ago
Closed 3 months ago
PR_Now() and Date.now() are out of sync on win32 XP/win7
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: chunmin, Unassigned)
References
Details
Per bug 1141415 comment 44, we need a way to make PR_Now() and Date.now() consistent on win32 platform(winXP and win7).
Comment 1•9 years ago
|
||
You can't make them consistent. They use different time sources that can have skew and are not terribly accurate anyway. Not to mention that they can both run backwards, which I expect is a problem for the use described in bug 1141415.
For consistent times within a process runtime you should use TimeStamp in C++ and performance.now() in JS, with the appropriate offsetting from one to the other based on what the zero
Updated•2 years ago
|
Severity: normal → S3
Comment 2•3 months ago
|
||
We dont support WinXP anymore.
Based on that, I will close this bug. :chunmin, please reopen if you disagree!
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•