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

Issue 879415 link

Starred by 5 users

Issue metadata

Status: Duplicate
Owner:
Closed: Sep 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

[User Feedback - Stable] Bookmarks Are Duplicating When Edited Instead of Updating (After Sync)

Project Member Reported by craigtumblison@chromium.org, Aug 31

Issue description

Chrome Version: 68.0.3440.106, 70.0.3537.0
OS Version: OS X 10.13.6

Hey all,

We're seeing some user reports that modifying a bookmark will cause a new sync item rather than replacing an existing one, creating duplicate bookmarks. This appears to be more pronounced the more devices you have syncing. Note that we found reports as far back as April, so this may not be related to a specific recent update.

Listnr (All Past 30 Days):
- https://listnr.corp.google.com/report/85630283247
- https://listnr.corp.google.com/report/85629723557
- https://listnr.corp.google.com/report/85629491420
- https://listnr.corp.google.com/report/85606504924
- https://listnr.corp.google.com/report/85591960466
- https://listnr.corp.google.com/report/85605846065
- https://listnr.corp.google.com/report/85597456500

Twitter (From Today):
- https://twitter.com/ArtemR/status/1035241935961612288
- https://twitter.com/steve_bishy/status/1035256031654424576

Community (Last Few Months):
- https://productforums.google.com/forum/#!topic/chrome/YkRa4_IA-p4
- https://productforums.google.com/forum/#!topic/chrome/NFxGXPeJiJY
- https://productforums.google.com/forum/#!topic/chrome/71mOs8n1_xg
- https://productforums.google.com/forum/#!msg/chrome/2gr0zOnC9uQ/WlgPFxhJCQAJ

I'm unable to reproduce this, so it could be specific to sync profiles. Let me know if there's specific troubleshooting data that may be useful.

Thanks!
 
Cc: krajshree@chromium.org
Labels: Needs-Triage-M68 Triaged-ET Needs-Feedback
Unable to reproduce the issue on mac 10.13.3 and win-10 using chrome reported version #68.0.3440.106 and latest canary #70.0.3537.0.
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened chrome browser.
2. Signed into chrome and synced everything.
3. Edited bookmark and observed that bookmark did not duplicate and got updated.

craigtumblison@ - Could you please check the attached screen cast and please let us know if anything missed from our end.

Thanks...!!
879415.mp4
758 KB View Download
krajshree@: Nope! I think your steps are accurate, this just may be difficult to reproduce. I don't see the behavior either, but we have enough reports that it may be worth digging deeper to see if there is an underlying cause. Thanks!
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 31

Labels: -Needs-Feedback
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
Labels: TE-NeedsTriageHelp
As per comment #3, it is not reproducible from TE-end. Hence, requesting someone from Services>Sync and UI>Browser>Bookmarks to please have a look into the issue and adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Owner: mamir@chromium.org
Over to mamir for consideration. Maybe there's another bug we can dupe this into? I vaguely remember that we've heard of this before.
Labels: Sync-Triaged
Mergedinto: 816723
Status: Duplicate (was: Unconfirmed)
Sorry but https://bugs.chromium.org/p/chromium/issues/detail?id=816723 is not public and we can't view its details.
Here is the main update on the other bug:
The code for synchronizing bookmarks across multiple devices is very old and hard to maintain or extend. We are in the process of migrating this code to the latest architecture of Chrome Sync. It's possible that many existing bugs are rooted in the old infrastructure. Together with the fact that the new infrastructure will make it much easier to identify and fix bugs, we would like to finish that migration and not modify the old implementation. We expect to rollout the new architecture towards the end of the year.
We are sorry if this has been a frustrating experience for you, but we believe that our chosen approach allows us to ship a better experience sooner.

Sign in to add a comment