Issue metadata
Sign in to add a comment
|
Tabs on other devices history is ~3 days out-of-date |
||||||||||||||||||||||
Issue descriptionChrome Version: 69.0.3497.21 OS: ChromeOS What steps will reproduce the problem? Unsure of what caused this. Used by Chromebox this afternoon, then got home and found that it listed it has having last been updated 3 days ago. What is the expected result? Expect that Tabs from other devices shows tabs opened today on Chromebox. What happens instead? Doesn't look like the tab history sync'd today. Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Aug 27
Mikel, maybe you can take a look, one you're back, since I think you're the last one, who worked with sessions.
,
Sep 3
Hi! Thanks wez@ for filing the bug and sorry for the delay, I was OOO. Can you still reproduce this problem? If yes, can you please attach chrome://sync-internals for *both* devices?
,
Sep 5
Re #3: Yes - if I load up the "Tabs from other devices" on my Chromebox, and on another device in the office, then it shows the Pixelbook I used at home last night as last having sync'd 3 days ago. I notice that the Chromebox & office device both show one another as sync'd just-now, so this may be an issue only with the Pixelbook. Unfortunately I don't have the Pixelbook immediately to-hand to get sync-internals from.
,
Oct 8
Hi wez@: is there any updates here? Any chance you've had or will have access to sync-internals in the Pixelbook? Thx!
,
Oct 14
Re #5: Unable to repro the issue right now; will take the Pixelbook to work so I can try again more easily on Monday.
,
Oct 15
The NextAction date has arrived: 2018-10-15
,
Oct 15
Not observing this issue any longer.
,
Oct 16
Thanks wez@ for reporting anyway! We've got another user complaining about a similar issue on Android, in https://bugs.chromium.org/p/chromium/issues/detail?id=894173. I think it's unrelated, but depending on the outcome there, we'll circle back. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by w...@chromium.org
, Aug 22