Closed
Bug 1688086
Opened 4 years ago
Closed 4 years ago
Unnecessary CPU usage on the main thread from compositor vsync notifications
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
86 Branch
People
(Reporter: mstange, Assigned: tnikkel)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: power, regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
When the compositor is registered for vsync, the vsync distribution mechanism doesn't only notify the compositor, it also dispatches a runnable to the parent process main thread to call NotifyGenericObservers
. This wakes up the event loop on the main thread and causes unnecessary CPU usage.
We should make sure that this runnable only gets dispatched if there are observers to notify.
Updated•4 years ago
|
Has Regression Range: --- → yes
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → tnikkel
Status: NEW → ASSIGNED
Updated•4 years ago
|
Blocks: power-usage
Updated•4 years ago
|
Keywords: regression
Pushed by tnikkel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bdf3ea4f60ba
Only dispatch a runnable to the main thread to notify it of vsync if there are main thread observers for it. r=mstange
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox86:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•