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

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


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@407930  917504  0.0      5  good
chromium@407940  913408  0.0      5  good
chromium@407945  915046  2243.47  5  good
chromium@407947  914227  1831.79  5  good
chromium@407948  925696  0.0      5  bad
chromium@407950  925696  0.0      5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 635857

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_tools-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:private_dirty_size_avg/load_tools_stackoverflow
Relative Change: 0.89%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2442
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004806947181572848


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

| 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/9004737664823797904

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


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@407930  917504  0.0      5  good
chromium@407940  913408  0.0      5  good
chromium@407945  915046  2243.47  5  good
chromium@407947  914227  1831.79  5  good
chromium@407948  925696  0.0      5  bad
chromium@407950  925696  0.0      5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 635857

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_tools-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:private_dirty_size_avg/load_tools_stackoverflow
Relative Change: 0.89%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2442
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004806947181572848


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

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

The bisect marked r407948 (V8 roll) as the most likely culprit, but failed to descend into it (issue 636310):

https://chromium.googlesource.com/v8/v8/+log/ddfecad0..f26eb821

cbruni,jkummerow,mlippautz: Could you please check if any of your patches might have caused the regression?

77d6ef3 [heap] ObjectStats: Fix off-by-one in histogram

This one is a fix for a histogram (otherwise accounted in wrong bucket), which is only enabled when running with --track-gc-object-stats or --trace-gc-object-stats.

9a6ee8d "[KeyedLoadIC] Support Smi "handlers" for simple field loads" saves some memory by avoiding handler compilation.

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