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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13f3a6f7640000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/13f3a6f7640000

Surface Synchronization: Enable by default on Android by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/5479bee2ba20c0527e19137d8056b539d30125d1
1.45e+08 → No values

Disable Surface Synchronization on Webview by nednguyen@google.com
https://chromium.googlesource.com/chromium/src/+/a91df97e284e497ecf1222b4ada5af66306718a5
No values → 1.543e+08

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Dave: my CL fixed the benchmark breakage but keeps being complained as causing significant regression. Is there anyway to relaunch all these bisect with my CL applied?

Hmm yea I notice the numbers before/after are not quite the same. We might be missing regressions due to the benchmark breakage. During my shift I filed many bugs that pointed to this CL.

 Issue 883786  has been merged into this issue.

 Issue 883473  has been merged into this issue.