Open Bug 1364230 Opened 8 years ago Updated 3 years ago

When compositing in the GPU process, the compositor thread in the parent process still receives Vsync notifications

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
All
Windows
Type:
defect

Tracking

()

People

(Reporter: mstange, Unassigned)

Details

See this profile, for example: https://perfht.ml/2pDsMaA The compositor thread in the parent process is mostly idle, because all the compositing is happening in the gpu process, but it still receives Vsync events and inserts markers for them. Not sure how much this matters but it might be a source of unnecessary wakeups.
Just a note that, when we fix this, we have to make sure they restart again if compositing transitions back to in-process.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.