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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgorPbpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4rzorQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgorfJuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4tHkrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopPYqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4vbJtgoM


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

Moving this nonessential bug to the next milestone.

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

Trying another bisect.

This seems very likely to be 7ea3a9cd847d7478598d22804d04c32c156c14f4. enne, just an FYI for you. No action needed since it was a revert.