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

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


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

android-nexus7v2

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

=== Auto-CCing suspected CL author adamk@chromium.org ===

Hi adamk@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Adam Klein
  Commit : 62f833774262be234e7d22fe3ea38ac06cc50669
  Date   : Thu Jul 20 21:49:48 2017
  Subject: Revert "[literals] Introduce CreateEmptyArrayLiteral Bytecode"

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_ebay
  Change       : 1.05% | 22339430.6667 -> 22574268.0

Revision                           Result                  N
chromium@488695                    22339431 +- 199527      6       good
chromium@488737                    22306833 +- 115387      6       good
chromium@488743                    22337212 +- 336866      9       good
chromium@488745                    22400700 +- 435348      9       good
chromium@488745,v8@b23b8c088c      22356668 +- 282052      6       good
chromium@488745,v8@8ab48b6c04      22348590 +- 453997      9       good
chromium@488745,v8@62f8337742      22630588 +- 154822      6       bad       <--
chromium@488745,v8@edc0eede74      22549107 +- 440669      14      bad
chromium@488745,v8@95fdc090ab      22605614 +- 231662      9       bad
chromium@488745,v8@f8a5c85da7      22584142 +- 511334      14      bad
chromium@488745,v8@6dce5c668d      22564654 +- 290399      9       bad
chromium@488746                    22615057 +- 208630      9       bad
chromium@488748                    22602769 +- 231373      6       bad
chromium@488758                    22592700 +- 286229      6       bad
chromium@488778                    22574268 +- 148079      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=load.search.ebay 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/8973190655576419216


For feedback, file a bug with component Speed>Bisection

My CL was a straight revert.