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

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


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

android-one
chromium-rel-win10

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_media/load_media_google_images

Revision             Result                 N
chromium@524993      4749720 +- 556534      21      good
chromium@525077      4820241 +- 173975      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=load.media.google.images 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/8958521343888613504


For feedback, file a bug with component Speed>Bisection

The alert has vanished.