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

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


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

android-nexus9

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@417863  10506683  109490   18  good
chromium@417869  10473312  94862.2  18  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 648268

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile
Test Metric: foreground-memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/http_en_m_wikipedia_org_wiki_Science
Relative Change: 0.48%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2114
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001077904692878112


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5891429711216640

| 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!

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

This looks like it's recovered, but didn't see an obvious commit/revert pair. Kicking another bisect to be sure.

Also moving sheriff from owner to CC.

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@417863  10477619  118771   8  good
chromium@417891  10455961  110438   8  good
chromium@417893  10495017  95499.8  5  good
chromium@417895  10692853  79064.3  5  bad
chromium@417898  10669721  46457.9  8  bad
chromium@417905  10675323  67782.5  5  bad
chromium@417919  10675456  61168.9  8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 648268

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
Relative Change: 1.67%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2164
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999519854448930384


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5902215707885568

| 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!

No owner, changing to untriaged.

Archiving as bisection is difficult and there's been no movement.