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

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


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

android-nexus5

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

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

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

Suspected Commit
  Author : hpayer
  Commit : 8833af23e9788c725b0887446915e4820383a385
  Date   : Fri May 05 11:24:02 2017
  Subject: [heap] Memory reducer calls GC with kGCCallbackFlagCollectAllExternalMemory flag.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_twitter
  Change       : 16.10% | 47973394.8571 -> 55697268.8889

Revision                           Result                    N
chromium@469654                    47973395 +- 16675111      14      good
chromium@469654,v8@25959abf79      47904652 +- 6042890       6       good
chromium@469654,v8@b7b3781b87      47032436 +- 4777324       6       good
chromium@469654,v8@8833af23e9      56760004 +- 5690796       6       bad       <--
chromium@469655                    53534881 +- 11971802      6       bad
chromium@469656                    54606441 +- 10862684      6       bad
chromium@469658                    57232420 +- 6356112       6       bad
chromium@469662                    56600503 +- 5718637       6       bad
chromium@469669                    54470124 +- 9293375       6       bad
chromium@469684                    56275553 +- 4825770       6       bad
chromium@469714                    51532433 +- 7571118       6       bad
chromium@469773                    55697269 +- 10879739      9       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.social.twitter system_health.memory_mobile

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

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


| 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 but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_twitter
  Change       : 14.22% | 46497629.2 -> 53107685.5238

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/b7b3781b8747d597cf0910c65221ad2b1881e0e4..d380c7da6df1fdd995688afd2c86a573852ecd73


Revision                           Result                    N
chromium@469654                    46497629 +- 48207375      20       good
chromium@469654,v8@b7b3781b87      48966369 +- 12988414      14       good
chromium@469654,v8@8833af23e9      ---                       ---      build failure
chromium@469654,v8@d380c7da6d      55503339 +- 16497099      9        bad
chromium@469654,v8@3d76d2a2dc      53434091 +- 18066599      14       bad
chromium@469654,v8@fbd7754947      55235605 +- 17601563      9        bad
chromium@469655                    54607035 +- 17001900      12       bad
chromium@469656                    52394329 +- 25747377      19       bad
chromium@469658                    54907833 +- 11270610      12       bad
chromium@469661                    54248619 +- 17544731      9        bad
chromium@469668                    55267155 +- 23317616      14       bad
chromium@469684                    53784241 +- 18816963      13       bad
chromium@469714                    56656804 +- 17117231      9        bad
chromium@469773                    53107686 +- 24948665      21       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.social.twitter system_health.memory_mobile

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

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


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