The long (1.9s and 1.8s) restyles suggest that entering/exiting fullscreen is the issue there. Hovering the first one, I see "FullscreenWillChange" in the first one, and "ExitFullscreenInDocTree" for the second one; and the Marker Chart shows long `FULLSCREEN_CHANGE_MS` markers for those whole jank periods (6.2sec for the first, 7sec for the second). So it looks like fullscreen operation is causing frontend to restyle itself which causes lots of invalidation, which then takes a while to process. (Probably due in part to the couple-hundred-tabs.) That's the worst offender in the profile from comment 7, but given that quadronom hasn't mentioned entering/exiting fullscreen so far, I'm wondering if that's tangential to the baseline perf issues that they're seeing. quadronom, are your issues generally related to moments when Firefox (or e.g. a YouTube video perhaps) enters/exits fullscreen?
Bug 1733227 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In the profile from comment 7 - 8, the long (1.9s and 1.8s) restyles suggest that entering/exiting fullscreen is the issue there. Hovering the first one, I see "FullscreenWillChange" in the first one, and "ExitFullscreenInDocTree" for the second one; and the Marker Chart shows long `FULLSCREEN_CHANGE_MS` markers for those whole jank periods (6.2sec for the first, 7sec for the second). So it looks like fullscreen operation is causing frontend to restyle itself which causes lots of invalidation, which then takes a while to process. (Probably due in part to the couple-hundred-tabs.) That's the worst offender in the profile from comment 7, but given that quadronom hasn't mentioned entering/exiting fullscreen so far, I'm wondering if that's tangential to the baseline perf issues that they're seeing. quadronom, are your issues generally related to moments when Firefox (or e.g. a YouTube video perhaps) enters/exits fullscreen?
In the profile from comment 7 - 8, the long (1.9s and 1.8s) restyles suggest that entering/exiting fullscreen is the issue there. Hovering the first one, I see "FullscreenWillChange" in the "First invalidated..." attribution, and "ExitFullscreenInDocTree" for the second one; and the Marker Chart shows long `FULLSCREEN_CHANGE_MS` markers for those whole jank periods (6.2sec for the first, 7sec for the second). So it looks like fullscreen operation is causing frontend to restyle itself which causes lots of invalidation, which then takes a while to process. (Probably due in part to the couple-hundred-tabs.) That's the worst offender in the profile from comment 7, but given that quadronom hasn't mentioned entering/exiting fullscreen so far, I'm wondering if that's tangential to the baseline perf issues that they're seeing. quadronom, are your issues generally related to moments when Firefox (or e.g. a YouTube video perhaps) enters/exits fullscreen?