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

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


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

android-nexus9

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

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

Hi vollick@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Use node() when generating element id's
Author  : vollick
Commit description:
  
The current code followed the lead of crrev.com/279553002 and
incorrectly used generatingNode, which lead to discrepancies
when animating pseudo elements. It seems that node() is the
correct choice, both here and in the CL I referenced.

BUG= 626571 

Review-Url: https://codereview.chromium.org/2141743002
Cr-Commit-Position: refs/heads/master@{#404921}
Commit  : 10b3fec07dfda5c362f1fc27a314468541c72ae0
Date    : Wed Jul 13 02:43:18 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@404895  6651676  0.0      5  good
chromium@404909  6651676  0.0      5  good
chromium@404916  6651676  0.0      5  good
chromium@404920  6651676  0.0      5  good
chromium@404921  7044892  0.0      5  bad    <--
chromium@404922  7044892  0.0      5  bad
chromium@404923  7044892  0.0      5  bad
chromium@404951  7044892  0.0      5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 639378

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_media_flickr
Relative Change: 5.91%
Score: 99.9

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


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

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

Appears to have recovered.