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

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


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

android-nexus5

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1497597d840000

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

Remove kHaveFutureData restriction from play state notifications. by dalecurtis@chromium.org
https://chromium.googlesource.com/chromium/src/+/b0ec93f6f1c9dd4754c813f198336a7a4c2f22a4

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

Huh, very weird. I wonder if something is getting into a spinloop.

Probable incoming duplicate of this is  bug 812719 : 3 more alerts came in for same range. Along with 12 *improvements*. I'm starting a bisect just in case, since the underlying commit for at least this issue and probably those 3 new alerts (#3) has now been reverted (https://chromium-review.googlesource.com/c/chromium/src/+/920481).

@#5 s/same range/similar range.

Fixed since was reverted. We can reevaluate if we attempt to remove this lie again.