ccing  stevet to get more inputs on this issue as the similar kind of issue fixed by him.

Steve is no longer working on this project. We can look into this on the sync side though to figure out if it's similar to that old issue.

valbulescu, what account are you syncing with? Could we get your permission to inspect the server data?

Also, does this reliably reproduce? 

It applies to my valbulescu@google.com account. if it is required for the
investigation, feel free to look at the data.

Can you confirm whether you have a default search engine set? i.e. Google is marked as (Default) in Manage Search Engines.

Google is the default search engine.

Looks related: https://bugs.chromium.org/p/chromium/issues/detail?id=443024

Pada tanggal 27 Mei 2016 04.07, "valbulescu@google.com via Monorail" <
monorail@chromium.org> menulis:

On what day did you first set the shortcut to "g"?

To be honest, I don't recall. I've done it several times until I realised
it keeps getting clobbered. I could set it again and report back if you
think it would help with testing?

The exact day isn't that important. But was it before May 3rd? 

I've set it to 'g' both before and after May 3rd.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8ec6ae8d86bc2badeb731ad4d85521d65aceae9c

commit 8ec6ae8d86bc2badeb731ad4d85521d65aceae9c
Author: pnoland <pnoland@chromium.org>
Date: Wed Jun 15 21:40:22 2016

[sync] Search engine shortcuts get underscores at the end after sync

Currently, search engines with matching prepopulate_id are treated as distinct if their keywords don't match. This can cause multiple copies of prepopulated search engines to be created; one copy with the original keyword and another copy with the modified keyword.

In the linked bug, the problematic behavior has created a different default search engine on each client. Deleting the non-default on client 1 is an attempt to delete client 2's default. There is sync code that assumes this was a mistake and resurrects the local default by appending an underscore.

This CL treats matching prepopulate_id as a conflict, and resolves it in favor of the remote search engine if the local engine isn't yet known to sync and was modified less recently. Note that this won't fix existing clients, whose duplicated engines will be known to sync already.

R=pkasting@chromium.org, zea@chromium.org

BUG= 613108 

Review-Url: https://codereview.chromium.org/2067723002
Cr-Commit-Position: refs/heads/master@{#400017}

[modify] https://crrev.com/8ec6ae8d86bc2badeb731ad4d85521d65aceae9c/chrome/browser/search_engines/template_url_service_sync_unittest.cc
[modify] https://crrev.com/8ec6ae8d86bc2badeb731ad4d85521d65aceae9c/components/search_engines/template_url_service.cc
[modify] https://crrev.com/8ec6ae8d86bc2badeb731ad4d85521d65aceae9c/components/search_engines/template_url_service.h

I have verified in the latest chrome dev (53.0.2782.0)and not able to reproduce. Looks like this got fixed. closing the bug.