I managed to reproduce the timeout twice on Windows 10, using Chromium 661171 (one of the 1st unstable revisions). You can see from the devtools logs that from a point on we're not getting the **fcp** metrics. This is what's causing the timeouts. I know we disabled metrics like these in the past. Should we consider disabling **fcp** also on Windows & re enable Chromium?
Bug 1554964 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I managed to reproduce the timeout twice on Windows 10, using Chromium 661171 (one of the 1st unstable revisions). You can see from the devtools logs that from a point on we're not getting the **fcp** metrics. This is what's causing the timeouts. I know we disabled metrics like these in the past. Should we consider disabling **fcp** also on Windows & removed the pinned Chromium versions?