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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=4a16738ec7ab364aa38ba7398e98831dab0e8e7dd1ba6f11b7282314592ea3c0


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

android-nexus6

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

=== 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_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_social/browse_social_instagram
  Change       : 2.02% | 53474321.3333 -> 54552081.3333

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/bdfd69a07ead07073c489c754322d51c790adebd..8ab48b6c04a71e0b834512833ef8b0fdaf6d2b05


Revision                           Result                   N
chromium@488719                    53474321 +- 1448978      9        good
chromium@488736                    53613610 +- 2247194      14       good
chromium@488745                    53366460 +- 909220       6        good
chromium@488745,v8@b23b8c088c      53693628 +- 575214       6        good
chromium@488745,v8@1084d20978      54051662 +- 1910104      14       good
chromium@488745,v8@bdfd69a07e      54254609 +- 2007846      21       good
chromium@488745,v8@69c8f16da7      ---                      ---      build failure
chromium@488745,v8@9d0438ba56      ---                      ---      build failure
chromium@488745,v8@8ab48b6c04      54654359 +- 1607714      14       bad
chromium@488746                    54440636 +- 723047       6        bad
chromium@488747                    54334140 +- 924079       9        bad
chromium@488749                    54476135 +- 871437       6        bad
chromium@488753                    54382382 +- 1304654      9        bad
chromium@488787                    54552081 +- 1288012      6        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.instagram system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973190759941562896


For feedback, file a bug with component Speed>Bisection

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

Three CLs in the range:

1: [WASM] Use scalar duplicate for matching shuffles on arm and arm64
2: [heap-profiler] Instrument JSPromise
3: [Turbofan] Merged the OSR phase into the graph building phase

Looks like 3 was reverted within the same range.

None of these seem super likely, have found a cleaner graph and re-bisecting: https://chromeperf.appspot.com/report?sid=7eccccdb8a2abadecac934843968900d8e21936e17563c61ee7d3cf6574d669e&rev=488787

[1]: https://chromium.googlesource.com/v8/v8.git/+/8ab48b6c04a71e0b834512833ef8b0fdaf6d2b05
[2]: https://chromium.googlesource.com/v8/v8.git/+/9d0438ba56cc1b88d45c9d67554ce8256fcbf90c
[3]: https://chromium.googlesource.com/v8/v8.git/+/69c8f16da7a9587d68904af36eb6ccac8ab5b1eb

=== 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_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:malloc:effective_size_avg/browse_social/browse_social_instagram
  Change       : 3.90% | 15545368.0 -> 16152283.4286

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/1125637681246fe2971d50fce2175615a766cbf9..858052930221bf05230d8e0eb0e681bf9b532980


Revision                           Result                   N
chromium@488719                    15545368 +- 1578618      14       good
chromium@488736                    15153171 +- 922009       6        good
chromium@488745                    15153014 +- 2087523      9        good
chromium@488745,v8@b23b8c088c      15783367 +- 1515400      14       good
chromium@488745,v8@48cee973c8      15683943 +- 1195371      9        good
chromium@488745,v8@a224eff455      15935121 +- 1083395      14       good
chromium@488745,v8@1125637681      15848844 +- 2121173      21       good
chromium@488745,v8@1084d20978      ---                      ---      build failure
chromium@488745,v8@b30ea1646a      ---                      ---      build failure
chromium@488745,v8@8580529302      16147089 +- 1313178      21       bad
chromium@488745,v8@8ab48b6c04      16185365 +- 1840292      21       bad
chromium@488746                    16439859 +- 1367724      14       bad
chromium@488747                    16310426 +- 1112234      9        bad
chromium@488749                    16301463 +- 1005638      9        bad
chromium@488753                    16464104 +- 1343163      9        bad
chromium@488787                    16152283 +- 2108757      14       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.instagram system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973093493050418944


For feedback, file a bug with component Speed>Bisection

This came back down eventually.