193399 - PR_Now returns incorrect time on WinNT4

Status: NEW

(NSPR :: NSPR, defect)

Description

[Warren Harris]

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.

Comment 1

[Warren Harris]

Attachment: 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 <[e-mail]>]

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months.
:KaiE, could you have a look please?
For more information, please visit auto_nag documentation.

Comment 3

[Kai Engert (:KaiE:)]

help reproducing this is welcome

Comment 4

[Kai Engert (:KaiE:)]

It seems a bit unlikely that we have such a serious incorrectness in a central time API.
If we still have it, nobody depends on it.
Someone with an NSPR development setup on Window should doublecheck if this can still be reproduced.