Open Bug 1941818 Opened 25 days ago Updated 10 days ago

Lots of time being spent updating intersection in parent process

Categories

(Core :: Web Painting, defect)

defect

Tracking

()

People

(Reporter: jrmuizel, Unassigned, NeedInfo)

Details

I noticed this happening recently. Not sure if it's reproducible yet. The refresh driver is being triggered by image animations. Not sure why computing intersections is so expensive. I have a lot of tabs.

https://share.firefox.dev/3DUfKBk

Do you know what we use intersection observer for in the parent?

Flags: needinfo?(emilio)

Did you have firefox view open / active or so? Looking at this the only one that can run in the parent seems to be some firefox view stuff...

The fact that's happening under an EnumerateSubDocuments call would support that theory... And that seems like a relatively recent change (bug 1868853).

Flags: needinfo?(emilio) → needinfo?(jmuizelaar)

Ah, no that's december 2023, huh. Still it seems the most likely candidate. We could / should add some markers to confirm the document we're updating, and maybe even the observer creation stack. But the document uri would be a good start.

Firefox view was active but probably not the currently displayed tab

Flags: needinfo?(jmuizelaar)

The severity field is not set for this bug.
:tnikkel, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(tnikkel)
You need to log in before you can comment on or make changes to this bug.