Please see the bug for the context.
Prior instrumentations showed:
The jank happens in more than 1 place:
URLRequest::Delegate::OnResponseStarted 34.3 jph
NetworkDelegate::OnRawBytesRead 16.4 jph
URLRequest::Delegate::OnReadCompleted 7.62 jph
... (the list continues, but further jankiness numbers are quite low)
I need to instrument
the code inside it to find out which part causes jank.
This is a 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. They've
helped to find and fix janky code. 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. The task gets created only in developer build and in Canary channel.
BUG=423948
TBR=jianli,danakj,jhawkins
Review URL: https://codereview.chromium.org/732633002
Cr-Commit-Position: refs/heads/master@{#304653}
81ef0df2b5