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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2NWZsgoM


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

android-nexus5X

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

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

Hi jam@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 : jam
  Commit : f307f287d11e34cee8507cf7cd04102479aa809e
  Date   : Tue Feb 07 17:47:30 2017
  Subject: Convert HandoffActiveURLObserver to use the new navigation callbacks.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_social/load_social_facebook
  Change       : 5.56% | 8317147.42857 -> 8258340.57143

Revision             Result                  N
chromium@448630      8317147 +- 2326467      14      good
chromium@448645      9407147 +- 55743.0      6       good
chromium@448654      9568256 +- 172950       6       good
chromium@448658      9852245 +- 134590       6       good
chromium@448660      9728341 +- 361623       6       good
chromium@448661      8258341 +- 2209015      14      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=load.social.facebook system_health.memory_mobile

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

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


| 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 Speed>Bisection.  Thank you!

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

bisect results don't make any sense, and this is a small regression only found on one page/device.