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

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


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

android-nexus7v2

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@430107  N/A   N/A      0  good
chromium@430172  N/A   N/A      0  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 667480

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=crowd720.vp9.webm.browser media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd720_vp9.webm_browser
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3502
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995349010174199904


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5305589968666624

| 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 Tests>AutoBisect.  Thank you!

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@430107  N/A   N/A      0  good
chromium@430172  N/A   N/A      0  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 667480

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=crowd720.vp9.webm.browser media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd720_vp9.webm_browser
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3504
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995339488161977136


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6079208604827648

| 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 Tests>AutoBisect.  Thank you!

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

This was just returning to its previous steady state value of ~600. It's probably not a real regression. I can't explain the ups and downs though. I can't imagine anything we do affecting browser memory so much.

That's good that it returned!

I think that if the bisect works, then it will teach us something helpful even if it isn't actionable now.

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : vm_proportional_set_size_delta/crowd720_vp9.webm_browser

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/fe64f860fd727cae179210713faee87b6c9e9209..778993dda4a5c8c4a15df8d8048165aa28b80ada


Revision             Result                  N
chromium@430107      204.667 +- 541.195      9      good
chromium@430124      168.5 +- 92.72          4      good
chromium@430132      174.5 +- 115.347        4      good
chromium@430136      207.8 +- 58.5047        5      good
chromium@430140      588.444 +- 108.702      9      bad
chromium@430172      571.375 +- 203.661      8      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 media.android.tough_video_cases

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

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


| 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 Tests>AutoBisect.  Thank you!

:( 95% sure nothing in the revision range causing this.

I'm closing wontfix.

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : vm_proportional_set_size_delta/crowd720_vp9.webm_browser


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=crowd720.vp9.webm.browser media.android.tough_video_cases

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

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


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