Closed
Bug 1585893
Opened 5 years ago
Closed 5 years ago
Investigate to use IDCompositionSurface instead of SwapChain with DirectComposition
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
INVALID
People
(Reporter: sotaro, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
For now, one triple buffered swap chain is used with DirectComposition. But if multiple overlays are used, it might be better to use IDCompositionSurface instead of SwapChain. For example, display timing might not be synchronized between SwapChains. We might get more performance. It seems that we could reduce memory usage. Though we do not know yet about the actual necessity.
Chromium uses IDCompositionSurface when DC layers usage is enabled.
https://cs.chromium.org/chromium/src/ui/gl/direct_composition_child_surface_win.cc?l=269
Reporter | ||
Updated•5 years ago
|
Blocks: WR-Win-Compositing
Reporter | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Priority: -- → P3
Reporter | ||
Comment 2•5 years ago
|
||
With Attachment 9098454 [details], when DCompositionSurface was used, rendering was slide down a bit. Origin of y seems different :(
Reporter | ||
Comment 3•5 years ago
|
||
It is not necessary anymore.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Attachment #9098454 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•