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

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


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

android-webview-nexus5X
chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1487cc60840000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1487cc60840000

Replace webgl_buffer_ in canvas and Remove ImageBuffer(Surface) etc
By xlai@chromium.org · Mon Jan 15 20:58:51 2018
chromium @ d02bb8346f13117d4a81d1124a3aeeaaed83ae99

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149cece1840000

This issue mixes up two different regressions together: 

1) There is a regression on system_health.memory_desktop and smoothness.tough_canvas_cases that were caused by my CL r529328. And this regression is already reported in https://bugs.chromium.org/p/chromium/issues/detail?id=803267, which has been fixed by r533820 and both benchmarks have returned back to normal.

2) There is another regression on jetstream. Based on the Performance dashboard, there are 11 bots that show regression on jetstream and quite a number of them have their regression build range outside my CL r529328. For
example, 

https://chromeperf.appspot.com/report?sid=6759aded51b30f9a1dada42f4a98e0e5530de18df1062276828a480e19a4e67a&rev=529357

In chromium-rel-win7-gpu-ati, the regression occurs for 529337 - 529357. 

The log range is https://chromium.googlesource.com/chromium/src/+log/f4f1bc7dbdc065b66aadcfcd3917dfcc9355ce0e%5E..813bf659ea6172e773b9a5dff7f75843ef65cbca?pretty=fuller&n=1000,

The narrowest build range is 529339-529347. I am unable to identify the CL that cause regression but it looks like https://chromium.googlesource.com/chromium/src/+/7bb0182173b755eeb617e4a215d65e13495f60a5 looks like a possible one.

Assigning to CL owner rjwright@chromium.org. If this is not caused by your change, please try to find a right owner and re-assign this issue. Thanks

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149cece1840000

[turbofan] trim effect chain nodes when they have no side-effect by tebbi@chromium.org
v8 @ e02f5611776106878720de2340e2eb098582cbe8

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Fixed by this revert: https://chromium-review.googlesource.com/c/v8/v8/+/883521