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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmoParAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6qPjwAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2ujIrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6vrz8QsM


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

android-nexus5X
android-nexus6
android-nexus7v2

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@406635  567412  414.569  8  good
chromium@406654  556794  30444.4  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 631033

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_media_9gag
Relative Change: 0.04%
Score: 0

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


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

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

This regression seems to have gone away.  I think we can close this.

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

Re-opening (improvement was most likely due to SH story set change).

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@406624  556482  30799.4  8  good
chromium@406655  545748  40417.6  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 631033

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_media_9gag
Relative Change: 0.00%
Score: 0

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


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

| 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/9004900541663192160

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [system health] Add flipboard to system health stories.
Author  : ulan
Commit description:
  
Flipboard on mobile exercises interesting workload,
where news items are rendered using canvas.

BUG=589726

Review-Url: https://codereview.chromium.org/2162873002
Cr-Commit-Position: refs/heads/master@{#406550}
Commit  : fd43bee2311ab250b3b6181ccd8be45092234eca
Date    : Wed Jul 20 14:30:46 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@406527  435848  0.0      5  good
chromium@406543  435611  529.501  5  good
chromium@406547  437845  4332.34  5  good
chromium@406549  435848  0.0      5  good
chromium@406550  479714  578.395  5  bad    <--
chromium@406551  497227  38668.5  5  bad
chromium@406559  514901  47488.3  5  bad
chromium@406591  550088  39032.8  5  bad
chromium@406655  550088  39104.4  5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 631033

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_media_9gag
Relative Change: 26.21%
Score: 95.0

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


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

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