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

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


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

chromium-rel-win8-dual

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12f2452d440000

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

cc: Support animated images in PaintFilters. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/0c568dc759c39d7598cfd811f7f2096daebc26c0

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

There are multiple changes to discardable image analysis, which is included in record_time, that went into that change. We include non-draw ops during the analysis, and also track HasDiscardableImages state for them correctly. Excluding both these changes locally and testing on Android Nexus5, I was able to recover the regression. But these things are necessary to support the use-case addressed in that patch. Also the regression is minor (~0.05ms in my local test).