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

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


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

chromium-rel-mac11

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14ce870e840000

📍 Found significant differences after each of 4 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14ce870e840000

Revert "DevTools: Initial implementation of Sampling Native Heap Profiler." by mastiz@chromium.org
chromium @ cb6090e4fb1211fc252941dec186096e937010fb

[Dice] Remove the SyncSetupInProgressHandle from DiceTurnSyncOnHelper by droger@chromium.org
chromium @ 2501f6f4e07ac2662c894a1c404de5bb5d8b3680

[ServiceWorker] Wrap Web*Callbacks thread safe for ServiceWorkerContextClient by leon.han@intel.com
chromium @ 8898229c569b5ed2f2e11510399669ba82ce45ad

[Dice] Add account image fetcher to AccountFetcherService by tangltom@chromium.org
chromium @ 067df55f3f4d665139956b2f8b4ad65a279d1bf9

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

Hi @tebbi@chromium.org, could you please explain what this means and what I have to do? It is the first time that I see a bug like this.

I'm sorry, I somehow missed your message. I'm not sure if this is still actionable, the regressed performance graph has no new data for months already.