Closed
Bug 1616594
Opened 4 years ago
Closed 4 years ago
Two frame builder configs during frame building
Categories
(Core :: Graphics: WebRender, task, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla75
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
in FrameBuidler::build
we pass a FrameBuilder
object coming from the render backend thread, as well as scene.config
. The two are not necessarily in sync and it's quite error-prone.
Let's have a single one or have separate types.
Updated•4 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•4 years ago
|
||
The render backend's frame builder config is kept only in order to send updates to the scene builder's frame builder config which will update the scene's in the next transaction. If need be the scene configs can be updated right away by looping over the documents. This avoids confusing bugs where only updating the backend's config affects the visibility pass but not the rest.
Depends on D63336
Updated•4 years ago
|
Assignee: nobody → nical.bugzilla
Status: NEW → ASSIGNED
Pushed by nsilva@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ae6a9e447f8d Use the scene's frame builder config during frame building. r=gw
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
You need to log in
before you can comment on or make changes to this bug.
Description
•