Comment 4 for bug 2048792

Hi All,

I'm a developer with Steve's group. Thank you for taking a look at this and linking to that other bug! I took a look through the profiler summaries linked in the thread and it appears very similar to what we are observing. We also captured performance profiles for the current version of Firefox we're using (100.0.2), and we observed similar behavior from the Renderer, Compositor, and SwComposite tracks.

Since we are unable to change Firefox version quickly in our use case, we would like to understand if there are any mitigations or settings we could modify to prevent these symptoms. The last comment in the linked bug thread mentions that disabling and re-enabling the Compositor resolved symptoms, so we will try this out tomorrow. Longer term though, upgrading the version is absolutely something we're looking at.

In addition to testing changes with the Compositor settings, are there any parameters we could change in the about:config page? In our initial testing, we have observed CPU usage vary roughly proportionately with the layout.frame_rate parameter when these CPU throttling symptoms are present (default was -1, and when we set to 30 or 15 for example, we see the CPU usage decrease).

We can also collect additional Firefox profiler results or other logs if they would help clarify the issue/symptoms.