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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6L6fvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqNTnuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqOSjtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqNTSvgoM


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

android-nexus5X
android-one

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

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

Hi alexclarke@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 : alexclarke
  Commit : 205b4a6222828e70127989c9451bbbd5e56be02d
  Date   : Fri Feb 03 19:30:16 2017
  Subject: Revert of Dont post delayed DoWork for disabled queues. (patchset #9 id:160001 of https://codereview.chromium.org/2572893002/ )

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max
  Change       : 28.77% | 43634654.1143 -> 56189980.2667

Revision             Result                   N
chromium@448045      43634654 +- 3798022      7      good
chromium@448046      56145311 +- 6217263      6      bad       <--
chromium@448047      56580206 +- 4937283      6      bad
chromium@448048      57354839 +- 4432759      6      bad
chromium@448050      55484423 +- 6104401      6      bad
chromium@448055      56526807 +- 5114580      6      bad
chromium@448065      56147705 +- 9154033      6      bad
chromium@448084      55013971 +- 6482694      6      bad
chromium@448123      56189980 +- 3297072      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 v8.mobile_infinite_scroll_tbmv2

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988295513054613632

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5215119832776704


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Well that's pretty strange, it's probably a bug that caused the memory to go down with that patch.

I do intend to try and re-land but I don't expect memory to go down!