New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 611322 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
ajha@chromium.org
hablich@chromium.org
█ brajkumar@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome not syncing it's time with system time

Reported by barricad...@gmail.com, May 12 2016 
Chrome Version       : 	50.0.2661.94 (Official Build) m (32-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
    Firefox: OK
         IE: OK

What steps will reproduce the problem?
(1) Open Chrome and execute some Javascript code in console to display current time ( new Date() will do)
(2) Move system time ( e.g. one hour ahead )
(3) Execute Javascript from step 1 again and notice that the time does not correspont to system time

What is the expected result?
Chrome should display correct system time.

What happens instead?
Chrome displays the old time for quite some time ( ranges from a few seconds to more than a minute, even if I open new tabs and pages )

Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by brajkumar@chromium.org, May 17 2016

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7 using chrome latest stable M50-50.0.2661.102 by following steps mentioned below.

1. Switched to chrome console
2. Typed new Date(), Observed the system time and date is displayed 
3. Changed system time to 1 hour ahead
4. Typed new Date(), Observed the system time and date is displayed as expected even after changing it.

Reporter@ - Could you please recheck this issue on latest chrome stable and kindly update the bug with latest behavior.

Thanks!
ConsoleDate&Time.png
171 KB View Download

Comment 2 by barricad...@gmail.com, May 22 2016 

Here's  a video  of said behaviour. ( the video is x264 encoded ).
x264.avi
340 KB Download
Project Member

Comment 3 by sheriffbot@chromium.org, May 22 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by brajkumar@chromium.org, May 23 2016

Labels: -Needs-Review Needs-Feedback
Owner: ----
No luck, Still not able to reproduce this issue on Windows 10 using chrome latest stable M50-50.0.2661.102. Observed chrome displays correct system time as expected.

Reporter@ - Is this issue seen on latest chrome canary M53-53.0.2746.0 as well? Could you please check it and kindly update this bug. You can download canary version from the below link.
https://www.chromium.org/getting-involved/dev-channel

Comment 5 by barricad...@gmail.com, May 24 2016 

This issue existed on Chrome Canary 52.0.2743.0 (64-bit) and still exists on version  53.0.2746.0 (64-bit). 

Interestingly, if system time is moved backwards instead of forwards, Chrome time is updated immediately.
Project Member

Comment 6 by sheriffbot@chromium.org, May 24 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by ajha@chromium.org, May 25 2016

Cc: hablich@chromium.org ajha@chromium.org
Components: Blink>JavaScript
Labels: -Type-Bug -Pri-3 -Needs-Review M-53 OS-Windows Pri-1 Type-Bug-Regression
Owner: ----
Status: Untriaged (was: Unconfirmed)
Able to reproduce this on the latest stable(50.0.2661.102) and the latest canary(53.0.2748.0) on Windows-7. Worked fine on Linux Ubuntu 14.04 with the same chrome versions and couldn't check on Mac OS 10.11.5 as it didn't allowed to change the system time.

Regressed in M-31:

Last good build: 31.0.1616.0
First bad build: 31.0.1619.0

Changelog:
https://chromium.googlesource.com/chromium/src/+log/04123796688783c8c1b8e2b330d201ef67470913..2a9fa873f683a2412e00499fb07ff92b4032778e

Unable to find the exact suspect, hence adding proper label for respective team to have a look at this.

Comment 8 by hablich@chromium.org, May 31 2016

Cc: u...@chromium.org
Status: WontFix (was: Untriaged)
This is afaik a known "special thing" with Windows which we cannot fix.

Comment 9 by barricad...@gmail.com, May 31 2016 

Could you provide some more info about it being a "special thing". I've tried doing some search but couldn't really find anything related to this issue.
►

Sign in to add a comment