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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqrOopgoM


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

android-nexus5

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979553882622348912

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979553874553365552

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_chrome/browse_chrome_omnibox
  Change       : 59.56% | 6.33733333333 -> 2.56266666667

Revision             Result                   N
chromium@470444      6.33733 +- 0.209736      6      good
chromium@470473      5.729 +- 2.66863         6      good
chromium@470487      6.0845 +- 0.454886       6      good
chromium@470489      5.73217 +- 2.29532       6      good
chromium@470490      2.59917 +- 0.320417      6      bad       <--
chromium@470491      2.57283 +- 0.185582      6      bad
chromium@470494      2.72217 +- 0.477184      6      bad
chromium@470501      2.56267 +- 0.251068      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.chrome.omnibox v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979553882622348912

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5862962637570048


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_chrome/browse_chrome_omnibox
  Change       : 58.37% | 6.16966666667 -> 2.56816666667

Revision             Result                   N
chromium@470444      6.16967 +- 0.712047      6      good
chromium@470473      6.33333 +- 0.830694      6      good
chromium@470487      6.34683 +- 0.843662      6      good
chromium@470489      5.7795 +- 2.71833        6      good
chromium@470490      2.61933 +- 0.376852      6      bad       <--
chromium@470491      2.64383 +- 0.456529      6      bad
chromium@470494      2.71667 +- 0.461339      6      bad
chromium@470501      2.56817 +- 0.377551      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.chrome.omnibox v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979553874553365552

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6055262550491136


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!