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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg75WXsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg78OHrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg78OdtwoM


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

android-nexus5X

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/1013
Failure reason: the build has failed.

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

There is a 25% (0.6 Mb) regression on code_and_metadata_size_max on browse_news_hackernews  benchmark. The code_and_metadata_size_avg also regresses slightly (by about 8%). Also the code_and_metadata_size_max drops every few runs. It is either in the range 3.3 or 2.7. I suspect it could be because of the timing of gc.

These benchmarks are now disabled. The graphs are also noisy.

Ned - can we delete this benchmark or disable it?

The benchmark should be removed in https://codereview.chromium.org/2711143002/

Reassign to mythria@ to land the CL

These benchmarks are removed in this cl: https://chromium-review.googlesource.com/c/451657/. 

I will also update the other cl to avoid confusion. I uploaded another cl, since rietveld couldn't process some of the changes. This change was submitted through gerrit. 

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