A bunch of low-hanging fruit for the next triager :)

mmenke: You are current triager. If any spare time worth taking some of these out. Also cc'ed next two triagers.

Has net team had any use for these trackers in the past? I have seen a few bugs indicating jank but I don't recall seeing anything actionable from them.

In general these seem useful if they work, so I just want to be sure that removing them is the right move.

mmenke: you didn't see any IO thread jank from these metrics from the extensions regression, right? That makes me suspect of the metrics.

I didn't, but only the first 30 seconds (And last 30 seconds?  Shutdown only, maybe?) of the browser's lifetime are included in them, and the issue was with stuff leaked over time, so not surprising.

Chris:  There's no chance I'll have time for this today.  Too many codereviews on my plate.

Do we need to look case by case to see if a metric should be added? If not, may I work on this or is anybody else working on this already?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Seems to be done.
https://cs.chromium.org/search/?q=ScopedTracker+&sq=package:chromium&type=cs