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

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


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

android-one

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435065  3207626  421491   27  good
chromium@435139  3241355  734877   27  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 671851

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=browse.social.twitter system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_twitter
Relative Change: 1.05%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1853
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993979004073884400


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

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

Most graphs have trended back to the pre-alert values but one is still a bit short.  May be worth keeping an eye on for a few more days to see if it fully recovers.

Bisect probably failed to reproduce due to  crbug.com/671156 . Bisecting using --story-filter on system_health.memory_mobile fails to reproduce.

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.