Incorrect handling of system date change
Reported by
tsarev...@targetprocess.com,
Jul 11 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: 1. Open a new tab. 2. Open developer console on it. 3. Type in 'new Date()', see current date. 4. Change system clock - move FORWARD for a one day. 5. Type in 'new Date()', see old current date from step 3. 6. If you move system clock backward, current date works well, so problem is for moving dates forward. 7. After some time current date begin to return correct date. Also, Firefox 39.0 works well, so the problem not system (?), but chrome one. What is the expected behavior? Expected date changed to a future one to reflect system clock changes. After some time all works well, so looks like it is bug in current date caching algorithm (mishandling moving current date forward) or smth similar. What went wrong? Current date is not updated in time after system clock update. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 May be issue related to incorrect V8 date caching?
,
Jul 11 2016
This reproduces on Windows 10, 52.0.2743.60
,
Jul 13 2016
Sorry, rechecked on Node.js 5.9.0 with:
node -p "while(true) { console.log(new Date()); }"
The problem persists, so issue is related to incorrect V8 system clock date forward handling.
,
Jul 13 2016
,
Jul 13 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 18 2017
,
Jul 18
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tsarev...@targetprocess.com
, Jul 11 2016