All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=851067

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=4f626c1b10edf81ddc37ceb0e6cb85b152134bf15232c9e3f14afb26e363947f


Bot(s) for this bug's original alert(s):

chromium-rel-win10

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1698a651240000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1698a651240000

[EventTiming] Remove the check of processing start being before onload by maxlg@chromium.org
https://chromium.googlesource.com/chromium/src/+/ddcf12998995d87b6fed15c881ac79dc57ff9e43
6.683e+06 → 8.78e+06 (+2.097e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

That's weird. My CL has nothing to do with file sizes. 

I think this might be a measure of used memory?

Oh, got it.

It might be too costly to create a timing object each time in order to check whether we should buffer a event timing entry.

The Pinpoint result is not right, my fault. Re-running now.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11f7b8e9240000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11f7b8e9240000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.

Those bots have churned through their queue now, going to re-run the job.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14fe5c1d240000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14fe5c1d240000

[Media Controls] Set overlay play button width/height dynamically by steimel@chromium.org
https://chromium.googlesource.com/chromium/src/+/3da026559a35a96de381e3a44cabfee364fae05b
6.683e+06 → 8.78e+06 (+2.097e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions