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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=adafdaa1fbc15991d797215209b195ac8b28c364dd044ab8ce405df3bd1fea59


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

chromium-rel-mac11
chromium-rel-mac11-pro

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

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

Hi hablich@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Michael Hablich
  Commit : af91eb85de58d9205f029da39662740ca7c222f2
  Date   : Wed Aug 23 10:18:57 2017
  Subject: Version 6.2.337.1 (cherry-pick)

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : oortonline_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/http___oortonline.gl__run
  Change       : 28.67% | 343929441.333 -> 442543693.333

Revision                           Result                    N
chromium@496123                    343929441 +- 112168       6      good
chromium@496416                    343820512 +- 274070       6      good
chromium@496563                    343877653 +- 260154       6      good
chromium@496636                    343908933 +- 207567       6      good
chromium@496655                    344040032 +- 997054       6      good
chromium@496660                    343855815 +- 189085       6      good
chromium@496661                    343943775 +- 193449       6      good
chromium@496661,v8@af91eb85de      444095692 +- 4585866      6      bad       <--
chromium@496662                    443027051 +- 4138309      6      bad
chromium@496664                    443289657 +- 5771178      6      bad
chromium@496673                    443003448 +- 5318981      6      bad
chromium@496709                    442543693 +- 6095593      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...oortonline.gl..run oortonline_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970304364716660384


For feedback, file a bug with component Speed>Bisection

 Issue 758856  has been merged into this issue.

 Issue 758853  has been merged into this issue.

This is the concurrent marker. 

Ulan: FYI, the "regressions" we talked about.

 Issue 758857  has been merged into this issue.

 Issue 758859  has been merged into this issue.

 Issue 758858  has been merged into this issue.

 Issue 758860  has been merged into this issue.

 Issue 758851  has been merged into this issue.

 Issue 758987  has been merged into this issue.

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Michael Hablich
  Commit : af91eb85de58d9205f029da39662740ca7c222f2
  Date   : Wed Aug 23 10:18:57 2017
  Subject: Version 6.2.337.1 (cherry-pick)

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : GC:duration_avg/browse_media/browse_media_flickr_infinite_scroll
  Change       : 165.04% | 65.4935 -> 173.5815

Revision                           Result                  N
chromium@496123                    65.4935 +- 47.419       6      good
chromium@496416                    74.128 +- 15.4836       5      good
chromium@496563                    373.369 +- 42.1095      5      good
chromium@496636                    379.706 +- 143.53       7      good
chromium@496655                    346.358 +- 139.019      6      good
chromium@496660                    352.296 +- 89.9254      6      good
chromium@496661                    356.544 +- 103.89       5      good
chromium@496661,v8@af91eb85de      179.449 +- 52.229       6      bad       <--
chromium@496662                    153.876 +- 30.0466      6      bad
chromium@496664                    175.397 +- 49.3009      6      bad
chromium@496673                    174.572 +- 49.1056      5      bad
chromium@496709                    173.582 +- 45.7311      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.flickr.infinite.scroll v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970270512573234272


For feedback, file a bug with component Speed>Bisection

Bisect in #15 is incorrect. Filed crbug.com/760478

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

I rekicked this with a smaller range and commented on crbug.com/760478

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Ulan Degenbaev
  Commit : d58937b88f53cd58b640ab3236596c7ac1efc5ba
  Date   : Tue Aug 22 18:14:38 2017
  Subject: [heap] Fix runtimestats scope for top-level GC tasks.

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : GC:duration_avg/browse_media/browse_media_flickr_infinite_scroll
  Change       : 466.21% | 74.6011666667 -> 422.395666667

Revision                           Result                  N
chromium@496123                    74.6012 +- 42.2895      6      good
chromium@496343                    64.4824 +- 32.1045      5      good
chromium@496453                    72.8605 +- 62.6122      6      good
chromium@496508                    77.5312 +- 55.1131      5      good
chromium@496536                    64.1416 +- 33.6384      5      good
chromium@496550                    72.0014 +- 44.1179      5      good
chromium@496557                    61.1575 +- 31.0614      6      good
chromium@496558                    63.4535 +- 22.8188      6      good
chromium@496558,v8@000ef276b1      64.6215 +- 44.5407      8      good
chromium@496558,v8@3710fd4a3d      54.9309 +- 15.1097      7      good
chromium@496558,v8@d58937b88f      376.572 +- 85.7314      5      bad       <--
chromium@496558,v8@c652a9eb2d      393.858 +- 39.7278      6      bad
chromium@496559                    342.789 +- 125.728      6      bad
chromium@496560                    352.539 +- 109.333      7      bad
chromium@496563                    422.396 +- 326.854      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.flickr.infinite.scroll v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969823221117198192


For feedback, file a bug with component Speed>Bisection

Issue 752116 has been merged into this issue.