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

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


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

chromium-rel-mac10

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

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

Hi kenrb@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 : Fix CrossProcessMouseEnterAndLeaveTest on Mac
Author  : kenrb
Commit description:
  
SitePerProcessBrowserTest.CrossProcessMouseEnterAndLeaveTest is failing
on the Mac continuous build. The logs appear to show that the event
targeting is missing the correct frames, which might be because of the
inverted y-axis affecting GetViewBounds(). This CL should fix that
problem.

TBR=avi@chromium.org
BUG=647202

Review-Url: https://codereview.chromium.org/2346843002
Cr-Commit-Position: refs/heads/master@{#418893}
Commit  : 201c93cdb160081b282f42075786282a5a9f43a8
Date    : Thu Sep 15 17:20:02 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@418828  1427319  10079.4  40  good
chromium@418890  1429485  12724.4  41  good
chromium@418892  1427138  9375.33  26  good
chromium@418893  1434466  11014.2  26  bad    <--
chromium@418894  1434047  11825.0  27  bad
chromium@418898  1430937  9346.72  27  bad
chromium@418906  1432690  11256.6  27  bad
chromium@418921  1433459  12000.1  41  bad
chromium@418951  1430748  9488.8   27  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 648165

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests oortonline_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max
Relative Change: 0.38%
Score: 95.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2388
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001105347756737328


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

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

Looks like the metric is too noisy for this small regression. The suspected CL cannot cause the regression.