Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression from 0.11.7 - wrong datetime shown for up to a minute after setting clock forwards #3199

Closed
net147 opened this issue Oct 6, 2015 · 5 comments
Labels
v8 engine Issues and PRs related to the V8 dependency. windows Issues and PRs related to the Windows platform.

Comments

@net147
Copy link

net147 commented Oct 6, 2015

On Windows 7:

  1. Run node.exe
  2. Enter "new Date()" and press enter
  3. Adjust the system clock by moving it forward a 3 minutes
  4. Press up and enter to repeat step 2. Notice the time shows the wrong value for minutes. This is incorrect for up to about a minute.

This issue occurs on Windows from Node.js 0.11.8 onwards. Doesn't seem to occur on Linux.

@net147
Copy link
Author

net147 commented Oct 6, 2015

This issue also occurs in Google Chrome.

@mscdex mscdex added windows Issues and PRs related to the Windows platform. v8 engine Issues and PRs related to the V8 dependency. labels Oct 6, 2015
@evanlucas
Copy link
Contributor

I believe v8 caches the date configuration and allows for a notification that date has changed. I would say this is working as expected though.

@evanlucas
Copy link
Contributor

Closing as this isn't really in our control. This is due to the way v8 caches the date/time

@net147
Copy link
Author

net147 commented Oct 20, 2015

Issue is tracked in Chromium project: https://code.google.com/p/chromium/issues/detail?id=17155

@evanlucas
Copy link
Contributor

Thanks @net147!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8 engine Issues and PRs related to the V8 dependency. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

3 participants