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

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


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

chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-dual

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

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/149e9607c40000

overview: Fix crash when closing windows. by sammiequon@google.com
https://chromium.googlesource.com/chromium/src/+/ee4464dd5fb288927155c3dd7b8bd3ea7bd78000

[heap] Clear from space after garbage collection. by hpayer@chromium.org
https://chromium.googlesource.com/v8/v8/+/494068c1c203a57bb094641ba9f366e82d03113c

Migrate WebApkIconHasher to SimpleURLLoader by pilgrim@chromium.org
https://chromium.googlesource.com/chromium/src/+/d6ac15840b5b7de8868d3d7e2d3074231425c353

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

Unless this is a webapk test, then it seems unlikely to be due to modifying WebAPK hash installer.  Unfortunately, there seems to be no deterministic process for determining if this test has anything to do with WebAPK.

The V8 heap change may cause this regression. I will have a look.

Issue 840700 has been merged into this issue.

Issue 839804 has been merged into this issue.

Issue 839801 has been merged into this issue.