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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16786036e40000

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

unsupported operand type(s) for +: 'float' and 'NoneType'

+Bisection, can anyone take a look at the pinpoint issue?

+backer, could you take a look? Looks like your change deal with GPU.

The only change of mine that I could find in that range was https://chromium-review.googlesource.com/c/1289513

I'm fairly certain that would not cause any regressions (it's unit tested and should be no-op unless we have driver bugs).

Did you have a different commit in mind?

Also that commit is now dead code on ToT. I have a CL up for review to remove it.

Reassigning back to maxlg@ to perform a bisect.