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

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


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

android-nexus9

Started bisect here:
https://chromeperf.appspot.com/buildbucket_job_status/9017928090410387200

The last one was successful, but it looks like the output has expired, and it didn't update the bug...

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@380889         71264.083333712.362453  12          good
chromium@378973         70578.5     372.556036  8           bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 591766

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests page_cycler.intl_ar_fa_he
Test Metric: vm_private_dirty_final_renderer/http___ynet.co.il_
Relative Change: 1.50%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/2851
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017928090410387200


| 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 label Cr-Tests-AutoBisect.  Thank you!

This memory usage increase in follows shortly after a decrease -- this is a revert of a recent apparent improvement, and in general we don't follow up on this kind of case.