summaryrefslogtreecommitdiffstats
path: root/device
diff options
context:
space:
mode:
authorvadimt <vadimt@chromium.org>2014-10-17 09:32:42 -0700
committerCommit bot <commit-bot@chromium.org>2014-10-17 16:33:09 +0000
commit176bcaf7c367523f1f5696a26dade1963b3b97b4 (patch)
treed409f406fe3b56e86b006cdfdf937fda5daed6ee /device
parent4a73ea3d91b615fefd45b730409b5f4bcc83720f (diff)
downloadchromium_src-176bcaf7c367523f1f5696a26dade1963b3b97b4.zip
chromium_src-176bcaf7c367523f1f5696a26dade1963b3b97b4.tar.gz
chromium_src-176bcaf7c367523f1f5696a26dade1963b3b97b4.tar.bz2
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. BUG=424359 TBR=pauljensen@chromium.org Review URL: https://codereview.chromium.org/661113002 Cr-Commit-Position: refs/heads/master@{#300115}
Diffstat (limited to 'device')
0 files changed, 0 insertions, 0 deletions