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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : vm_private_dirty_delta/video.html?src_tulip2.mp3_type_audio

Revision             Result                  N
chromium@468687      1624.76 +- 4012.65      21      good
chromium@468774      1271.81 +- 2392.08      21      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=video.html.src.tulip2.mp3.type.audio media.android.tough_video_cases

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

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


| 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!

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

=== Auto-CCing suspected CL author pdfium-deps-roller@chromium.org ===

Hi pdfium-deps-roller@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : pdfium-deps-roller@chromium.org
  Commit : 84d501e5e0fa77f126b6895ebda8695094bb6883
  Date   : Tue May 02 17:08:08 2017
  Subject: Roll src/third_party/pdfium/ ea23e0a2d..ec3a9e27d (1 commit)

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : vm_private_dirty_delta/video.html?src_tulip2.mp3_type_audio
  Change       : 52.74% | 2876.0 -> 1359.33333333

Revision             Result                  N
chromium@468687      2876.0 +- 1025.48       6      good
chromium@468688      1730.67 +- 1026.62      6      bad       <--
chromium@468689      1413.33 +- 940.105      6      bad
chromium@468690      1558.0 +- 994.107       6      bad
chromium@468693      1232.0 +- 1102.78       6      bad
chromium@468698      1207.33 +- 964.413      6      bad
chromium@468709      1089.33 +- 906.186      6      bad
chromium@468731      1224.0 +- 1082.53       6      bad
chromium@468774      1359.33 +- 921.067      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=video.html.src.tulip2.mp3.type.audio media.android.tough_video_cases

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

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


| 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!

I've reported this as a bad bisect. PDFium is not used in Chromium Android, so it cannot have an impact on Android benchmarks.

WontFix. Bisect didn't work and bug is stale.