PR_Now returns incorrect time on WinNT4

NEW
Assigned to

Status

NSPR
NSPR
16 years ago
12 years ago

People

(Reporter: Warren Harris, Assigned: Wan-Teh Chang)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
Wan-Teh: Here's the time problem I mentioned to you yesterday. It looks like
PR_Now (not PR_ExplodeTime) is doing the wrong thing on NT4. The microsec count
it returns is exactly 9 hours different on NT4 versus Win2K and Win98 (could be
time-zone dependent). I'll enclose a test case.
(Reporter)

Comment 1

16 years ago
Created attachment 114481 [details]
test case

Result on NT4.0 SP6:
 
PR_Now time = 1045225565291000 us, 17420426 mins
PR_ExplodeTime = 26 min, 12 hr
PR_FormatTimeUSEnglish = [Feb 14 12:26:05]

Result on Win2K one minute later:
 
PR_Now time = 1045258053309000 us, 17420967 mins
PR_ExplodeTime = 27 min, 21 hr
PR_FormatTimeUSEnglish = [Feb 14 21:27:33]
 
Note the minute count from PR_Now() is out by 541 minutes or ~9 hours which is
the current GMT offset for PST.


[contact John Wainwright <john@kontiki.com>]
QA Contact: wtchang → nspr
You need to log in before you can comment on or make changes to this bug.