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

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


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

health-plan-clankium-phone
perf-go-phone-1024

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

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

Hi perezju@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 : Juan Antonio Navarro Pérez
  Commit : 2200b6d949dc8b19a65c3e1a0753479ee68d3d65
  Date   : Fri Jul 06 10:14:12 2018
  Subject: Revert "gpu: Share GrContext between RasterDecoders for OOP raster."

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 22.66% | 24300589.3333 -> 29807661.3333

Revision                                       Result                  N
android-chrome@464aed2314                      24300589 +- 220065      6      good
android-chrome@77fc3d2fb3                      24474669 +- 313969      6      good
android-chrome@77fc3d2fb3,chromium@572931      24472109 +- 264645      6      good
android-chrome@77fc3d2fb3,chromium@572932      24329603 +- 155635      6      good
android-chrome@77fc3d2fb3,chromium@572933      29799128 +- 233395      6      bad       <--
android-chrome@77fc3d2fb3,chromium@572935      29768579 +- 231870      6      bad
android-chrome@789b37ba6d                      29938221 +- 291406      6      bad
android-chrome@fb25449d26                      29807661 +- 370300      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.chrome.newtab 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/8941369541635736800


For feedback, file a bug with component Speed>Bisection

Expected regressions on few metrics that had improved when the origina CL landed.