Adding instrumentation to locate the source of jankiness
commita23c1c6d16f59e5adfe79beabb94e18e31a73ab0
authorvadimt <vadimt@chromium.org>
Mon, 20 Oct 2014 22:40:15 +0000 (20 15:40 -0700)
committerCommit bot <commit-bot@chromium.org>
Mon, 20 Oct 2014 22:41:01 +0000 (20 22:41 +0000)
tree9ed60aca7ede017f6c58d103b51fc2eb0acd1994
parentf898f99146b7cde544c9c10d7cbe9861a6c71bc5
Adding instrumentation to locate the source of jankiness

Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after.
A number of similar CLs were landed, and none of them caused issues. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers.
Landing as TBR since this is a mechanical, safe and temporary change.

This CL instruments most popular OnRefreshTokenAvailable overrides.

BUG=422460
TBR=jam@chromium.org, zelidrag@chromium.org, erikwright@chromium.org

Review URL: https://codereview.chromium.org/643183003

Cr-Commit-Position: refs/heads/master@{#300361}
chrome/browser/policy/cloud/user_policy_signin_service.cc
chrome/browser/sync/profile_sync_service.cc
components/signin/core/browser/account_tracker_service.cc
components/signin/core/browser/signin_account_id_helper.cc
google_apis/gaia/account_tracker.cc
google_apis/gaia/identity_provider.cc