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

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


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

chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win7-gpu-ati
chromium-rel-win8-dual

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14977b00c40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14977b00c40000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/148c306cc40000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16b7d59cc40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/148c306cc40000

tracing: TracingController -> Coordinator by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/c77b44ebb53886e039c8471548c2050cceceda59

Get navigation info without using FrameLoader snapshots by dproy@chromium.org
https://chromium.googlesource.com/catapult/+/5d35a2c7122c1ac4a9a37e7743a19f628f25a38b

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

Unduplicating upon further investigation - it doesn't look like the navigation start event for FMP changed so this is not because of my CL. 

Looks like the metric was broken for a quite a few commits in the middle, and the traces before and after look really different. Are we using a different page now? For example, before the regression, the LocalFrameView::performLayout task takes 214ms, but after the regression, it is taking 538ms.

Unassigning myself because I don't have enough context to debug this. 

📍 Found significant differences after each of 5 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16b7d59cc40000

[Chromoting Add codec parameter for all payload types by zijiehe@chromium.org
https://chromium.googlesource.com/chromium/src/+/f912ff75b23440a67e3674064db799c0f15a7602

tracing: TracingController -> Coordinator by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/c77b44ebb53886e039c8471548c2050cceceda59

Update VR test APKs to v1.10 by bsheedy@chromium.org
https://chromium.googlesource.com/chromium/src/+/e825ae73219e421007090602d3abb04861a712ba

Text-decoration-skip to text-decoration-skip-ink with initial value auto by drott@chromium.org
https://chromium.googlesource.com/chromium/src/+/cc22f53f9455428f8d6ad59633730e6d4e7b5273

Background color for StackView snapshot animations by gambard@chromium.org
https://chromium.googlesource.com/chromium/src/+/5b35d0e9b9a2f54b58ad2535398c22bb8f473532

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

My change
[Chromoting Add codec parameter for all payload types by zijiehe@chromium.org
https://chromium.googlesource.com/chromium/src/+/f912ff75b23440a67e3674064db799c0f15a7602
impacts chromoting only.

My change
Background color for StackView snapshot animations by gambard@chromium.org
https://chromium.googlesource.com/chromium/src/+/5b35d0e9b9a2f54b58ad2535398c22bb8f473532
impacts Chrome on iOS only. If I understand correctly, the problem is affecting desktop.

Unassigning myself.