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

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


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

android-webview-nexus6

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

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

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.

Blocking on  crbug.com/862654  - Pinpoint failure locating isolate hash.

 Issue 862654  is fixed. I'm re-running these jobs.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/145ef972a40000

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

Turn on OOP Raster on android bots by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/d82c4fabc5cc6cbe6b475186ed9fa0216980e533
146 → 224.7 (+78.73)

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

I suspect that this maximum queuing time increase is the same as  issue 860177 .  I'll retry this with a warm shader cache to see if this has the same root cause.

I got some traces back from the webview bot, and this looks identical to the reasoning in  issue 860177 .  My interpretation here is that this is unpreemptable shader compilation that is causing the max expected queuing time to increase.