Open
Bug 830218
Opened 13 years ago
Updated 4 years ago
Progressive Draw causes recomposites when updating displayport outside the screen
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
NEW
People
(Reporter: BenWa, Unassigned)
Details
STR:
1) Turn on the new cleopatra feature 'Show Frames Boundary'.
2) Looking at a task.js profile the last few frames where progressive draw transaction come in we composite new frames even if we're updating outside the screen.
This is mostly a battery usage issue.
Comment 1•13 years ago
|
||
Interesting - pretty minor though. I wonder how the hit of checking whether contents is on the screen or not compares to just doing the composite...
Updated•4 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•