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

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


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

android-webview-nexus6

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

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

Hi altimin@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 : Alexander Timin
  Commit : e923e29452d33a3756563b8e232a34455fdbd53e
  Date   : Mon Dec 11 17:49:20 2017
  Subject: [scheduler] Trace pre-task and post-task observers in TQM

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : textarea-parsing/textarea-parsing
  Change       : 11.16% | 333.997864366 -> 296.719062445

Revision             Result                  N
chromium@523080      333.998 +- 7.68804      6      good
chromium@523107      346.383 +- 4.52531      6      good
chromium@523120      343.429 +- 5.66973      6      good
chromium@523124      342.605 +- 6.15941      6      good
chromium@523126      340.968 +- 7.5497       6      good
chromium@523127      296.635 +- 3.58719      6      bad       <--
chromium@523133      296.719 +- 2.15727      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

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

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


For feedback, file a bug with component Speed>Bisection

This is the result of adding extra tracing and with tracing disabled there is no change in performance, therefore closing as wontfix.