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

Issue 672558 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 639009
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Old Android tabs not syncing properly

Project Member Reported by maxbogue@chromium.org, Dec 8 2016

Issue description

via 565481#c22 by clopes@gmail.com. Nicolas, can you take this since you're already doing a lot of work on sessions?

---

I still have a problem that I believe is part of this bug as it was merged in from  bug #488743 

Exact same issue as when I reported the bug over a year ago...

Summary: Chrome on Android does not sync all tabs outbound (some are missing on other devices)

Details:
Steps to reproduce the problem:
1. Open several tabs on Chrome Android over many months of use and keep them open
2. Go to Chrome on desktop and the History view
3. See the Android device and its tabs, but only an arbitrary subset of the tabs that are open on the Android device

What is the expected behavior?
All tabs that are open on the Android device are visible on the other (Desktop) device

What went wrong?
See above

Did this work before? No 

Chrome version: 55  Channel: stable
This is on Android 7 and Windows 10

I suppose Chrome on Android has a different actual implementation of "open tabs" than on Desktop.  In other words, a Chrome process may not even be running on Android and all of the listed tabs may not actually even really be open.  E.g. they only get (re-)opened when you tap on them after some period where they become stale or the device/app starts to de-allocate them to save resources.  But nonetheless the user experience should not reveal this fact when syncing.  So, if the tab shows up in the "open" tabs list on Android, then it should show up on all other synced devices, regardless of how long ago it was opened or if it is truly open from a technical implementation standpoint.
 

Comment 1 by zea@chromium.org, Dec 8 2016

Mergedinto: 639009
Status: Duplicate (was: Assigned)
Yeah, this is the same issue as 639009. I'm in the process of trying to fix it.

Sign in to add a comment