Navigation start to commit trace
BUG=part of 585134 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation This is a part of the design for 585134 which includes a larger set of traces. As part of that design we also noticed overlapping traces that existed earlier for navigation start to commit. As discussed with carlosk@, this change also reverts the earlier traces which only covered PlzNavigate and adds the new traces that cover the following scenarios: - plzNavigate and traditional flows - committed and aborted/failed/canceled loads This patch adds the async begin and end traces in the constructor and destructor of NavigationHandleImpl respectively. That would cover all of the scenarios as detailed in the design doc (https://docs.google.com/a/chromium.org/document/d/1yM2khCxLC5AV3X4y7cyuCNCFHCmq9CpqQzDwK6MROaw/edit?usp=sharing). The start time of Navigation is passed in the constructor and that would be used as the trace start timestamp. For failed/aborted provisional loads, the argument net error code will give the error code. In this patch I am adding them in the existing "navigation" category only and later they might be extended for new categories like "loading". Review URL: https://codereview.chromium.org/1825533002 Cr-Commit-Position: refs/heads/master@{#389881}
Showing
Please register or sign in to comment