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

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


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

android-nexus5

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

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

Hi mstarzinger@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 : Michael Starzinger
  Commit : 02d201bfdd18f1292146dd32bcca911c3465a991
  Date   : Wed Dec 06 10:14:58 2017
  Subject: Enable --write-protect-code-memory by default.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/cold_Regular-3G/FlipBoard
  Change       : 3.12% | 1022.55933333 -> 1054.499

Revision                           Result                  N
chromium@522320                    1022.56 +- 10.8374      6      good
chromium@522324                    1015.25 +- 9.12707      6      good
chromium@522325                    1020.87 +- 11.6557      6      good
chromium@522325,v8@2290ad8b55      1022.18 +- 11.1567      6      good
chromium@522325,v8@3c778f559c      1023.36 +- 15.9654      6      good
chromium@522325,v8@c09b66b84f      1016.04 +- 9.80098      6      good
chromium@522325,v8@02d201bfdd      1059.47 +- 8.57419      6      bad       <--
chromium@522325,v8@61493f5bdd      1057.89 +- 19.9637      6      bad
chromium@522326                    1052.75 +- 10.0516      6      bad
chromium@522328                    1050.01 +- 5.12809      6      bad
chromium@522336                    1049.04 +- 17.7689      6      bad
chromium@522352                    1044.35 +- 10.8983      6      bad
chromium@522383                    1054.5 +- 8.09492       6      bad

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=FlipBoard loading.mobile

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

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


For feedback, file a bug with component Speed>Bisection

mstarzinger: did you have a chance to take a look at this regression yet? cc kouhei, owner of the benchmark, to comment on how important it is to look at a 3% regression.

 Issue 795000  has been merged into this issue.

 Issue 794992  has been merged into this issue.

This is old enough that we should likely WontFix. mstarzinger@, can you confirm?

Confirmed.