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

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


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

android-webview-nexus6

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14bcac64840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14f8b1b4840000

Re-kicked bisect.

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14bcac64840000

[viz] Implement local resource in GLRenderer
By xing.xu@intel.com · Fri Dec 22 02:20:01 2017
chromium @ 9cc56b283e51de94cc373a77214da2bb646efcbd

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Hi, doesn't this duplicate issue https://bugs.chromium.org/p/chromium/issues/detail?id=797390?

It seems memory:chrome:all_processes:reported_by_chrome:gpu:effective_size goes from 1248312.0 to 1685112.0.

As investigated in 797390. This CL moves memory::gpu to memory::cc. So if we want to verify if this is real memory regression, we have to collect data about memory:chrome:all_processes:reported_by_chrome:cc:effective_size

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14f8b1b4840000

[viz] Implement local resource in GLRenderer
By xing.xu@intel.com · Fri Dec 22 02:20:01 2017
chromium @ 9cc56b283e51de94cc373a77214da2bb646efcbd

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

You can dupe it over

Hi,as we have reached a consensus, this isn’t memory regression, but memory was calculated from cc tag to gpu tag. And the new memory tag viz will be used instead(crbug.com/800238). So how about close this one and track it in the viz memory dump issue?