Issue metadata
Sign in to add a comment
|
Timezone within chrome resets to gmt+0000 automatically (PC in correct timezone)
Reported by
osandake...@gmail.com,
Nov 4
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3595.2 Safari/537.36 Example URL: Almost every social media site. fb/messenger/whatsapp/reddit Steps to reproduce the problem: 1. Leave the browser open 24x7 2. Eventually timestamps on social media is wrong What is the expected behavior? Timestamps (newsfeed, chats etc) should match with local timezone What went wrong? Computer is set to gmt+0530 and it stays however chrome goes back gmt+0000 eventually. Interestingly this happens around 10-11am everyday. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes I am not certain. At that time I was on canary, now on dev Does this work in other browsers? N/A Chrome version: 72.0.3595.2 Channel: dev OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I keep the browser running for days. Once this bug is occurred, simply closing n reopening chrome fixes bugged timestamps to match local timezone There is a 3rd party extension that logs whatsapp activity of a user and I believe it uses some sort of date/time commands to retrieve timestamps. That may cause the issue however it did work fine until chrome v70 or so for few weeks. github [DOT] com/supernova13892/whatsapp_stalker/ Console log once timezone bug occurs. Usually occurs around 10-11am local time everyday since 2 weeks I believe. ---------- 11:09:55.075 inject.js:102 <User> was online at Tue Oct 23 2018 11:09:54 GMT+0530 (GMT+05:30) 11:10:01.077 inject.js:102 <User> was online at Tue Oct 23 2018 11:10:00 GMT+0530 (GMT+05:30) 11:10:07.079 inject.js:102 <User> was online at Tue Oct 23 2018 11:10:06 GMT+0530 (GMT+05:30) 06:39:18.893 VM45:1243 User is online 06:39:21.254 inject.js:102 <User> was online at Tue Oct 23 2018 06:39:20 GMT+0000 (GMT) 06:39:27.184 inject.js:102 <User> was online at Tue Oct 23 2018 06:39:26 GMT+0000 (GMT) 06:39:33.184 inject.js:102 <User> was online at Tue Oct 23 2018 06:39:32 GMT+0000 (GMT) ----------
,
Nov 5
Unable to reproduce the issue on chrome reported version# 72.0.3595.2 using Windows-10 with steps mentioned below: 1) Launched chrome reported version and logged-in into fb with valid credentials 2) Pinged from logged-in account and compared time with local system timing, waited for 1hr and again pinged from same logged-in account, observed the time in fb is similar to system timing @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging it in better way and let us know if this issue is specific to gmt+0530. Thanks!
,
Nov 5
Hello, Thanks for the response. Its rather strange but timebug occurs only ONCE a day at around 10-11am. It did happen for today already and simply closing and reopening browser did fix the shifted times, to attach a screenshot I have to wait till usual trigger time tomorrow (yes I kept track of it for almost a month now) As for now I will explain change in timestamps in text. Lets take that video you attached, 246pm (+530) is correct time. Once the bug occurs it simply appears as 9.16am (5 hours and 30 minutes behind) and refreshing the page doesnt fix the issue. Also it affects multiple tabs, fb newsfeed timestamps, chat times (messenger.com), and journaling site I use (monkkee.com) I have a suspicion that external plugin I loaded may have caused the issue but then again chrome ran with it for almost a month (till late sep to late oct) without any issue in changes of timestamps. [Furthermore, extension first loaded on 28th of sep and first time timestamps got messed up was 19th oct. Till then chrome ran fine 24x7 no issues] Also I did not change anything in operating system nor installed any new applications otherthan updating existing ones anyway I will attach a list of programs and startup items just to make sure any external program is causing the issue. https://imgur.com/a/vn0xbIn I did attach some screenshots and made a album. Please look through it and hopefully that helps. Tomorrow I will attach a pic of changes of timestamps in social media sites. Thanks again.
,
Nov 5
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 6
Hello, It happened again. Therefore im attaching more screenshots of the issue. (shifted times vs. correct times after restarting browser) Almost every tab opened are affected and refreshing does not fix the issue somehow closing and reopening the browser does. Please look into it. Thank you. https://imgur.com/a/syUz0kt
,
Nov 6
Tentatively adding Blink>Javascript component to it and cc'ing: jshin to help in providing further inputs on this issue. Thanks!
,
Nov 8
Can reproduce on Canary 72.0.3592.0 : javascript:new%20Date().toString() shows GMT+0000 , while Beta and Dev (72.0.3602.2) show (my) correct GMT+0200 Affects eg. email timestamps in Gmail.
,
Nov 8
Likely related : https://crbug.com/854387 (and the bugs blocking and merged in it)
,
Nov 9
osandakeshan/jshin@ Could you please confirm if this issue is similar to Issue: 854387, this will help us in triaging it further. Thanks!
,
Nov 9
Yes, except in my case its triggered at certain time (around 10/11am local) every single day if i kept the browser open. Simply closing and reopening fixes the bug temporary for 24 hours and it keeps on happening everyday at same exact time. I still couldn't manually trigger it though. Chrome: 72.0.3602.2 (Official Build) dev (64-bit) (cohort: Dev) Platform: Win 7 SP1_U en_us x64
,
Nov 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Nov 4