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

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


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

android-nexus6
android-one
chromium-rel-win10

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

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

Hi mstensho@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 : Morten Stenshorne
  Commit : 181b2de767ae078de4e6cc03e31072afe5708965
  Date   : Fri Jan 05 09:13:39 2018
  Subject: [LayoutNG] Better column balancing, paying attention to space shortage.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : large-table-background-change-with-invisible-collapsed-borders/large-table-background-change-with-invisible-collapsed-borders
  Change       : 6.81% | 776.33 -> 829.22

Revision             Result                  N
chromium@527196      776.33 +- 18.225        6      good
chromium@527236      766.253 +- 10.6909      6      good
chromium@527241      737.812 +- 15.8341      6      good
chromium@527243      758.381 +- 34.8157      9      good
chromium@527244      791.778 +- 44.1178      5      bad       <--
chromium@527246      783.122 +- 24.1372      6      bad
chromium@527256      783.179 +- 29.983       9      bad
chromium@527276      829.22 +- 52.3396       6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.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 blink_perf.paint

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8957932115982209920


For feedback, file a bug with component Speed>Bisection

That CL only changes LayoutNG code, which isn't enabled by default.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12c8991b040000

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                  N
chromium@527248      2395891 +- 64912.9      21      good
chromium@527268      2399221 +- 61818.0      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=http.m.intl.taobao.com.group.purchase.html memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8957865811246539296


For feedback, file a bug with component Speed>Bisection

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12c8991b040000

Several regressions in this bug were unrelated and also recovered. I removed them. The remaining regressions are <200KiB and not reproducible in bisect. WontFix-ing.