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

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


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

chromium-rel-mac10

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

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

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

===== 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@409157  2582486  6608.71  12  good
chromium@409171  2586419  7875.01  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 634400

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_social_instagram
Relative Change: 0.35%
Score: 0

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


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@409132  2567462  28.6217  5   good
chromium@409152  2567816  6641.06  12  good
chromium@409155  2573960  7710.46  12  good
chromium@409156  2566643  7338.79  5   good
chromium@409157  2585391  7570.43  8   bad
chromium@409162  2583859  9027.14  8   bad
chromium@409171  2588975  9977.44  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 634400

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_social_instagram
Relative Change: 1.05%
Score: 0

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


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@409132  2567462  28.6217  5   good
chromium@409152  2567816  6641.06  12  good
chromium@409155  2573960  7710.46  12  good
chromium@409156  2566643  7338.79  5   good
chromium@409157  2585391  7570.43  8   bad
chromium@409162  2583859  9027.14  8   bad
chromium@409171  2588975  9977.44  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 634400

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_social_instagram
Relative Change: 1.05%
Score: 0

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


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

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

kojii: The bisect marked your patch (https://codereview.chromium.org/2192703002) as the culprit for this regression (+18 KiB in partition_alloc on instagram). Please investigate and decide on further action.

Looks like the same issue as  issue 633943 , should I keep both of them, or handle as duplicate?

I'm looking into it anyway.

I'd mark them as duplicates ;-)

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

===== 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@409132  2572254  6503.29  12  good
chromium@409171  2580775  8968.37  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 634400

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_social_instagram
Relative Change: 0.32%
Score: 0

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


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

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