Closed Bug 1405241 Opened 2 years ago Closed 2 years ago
Render Bridge Child::Recv Wr Updated() could receive same wr::Id Namespace
This bug is created based on Bug 1404232 Comment 7. WebRenderBridgeChild::RecvWrUpdated() sometimes received same wr::IdNamespace since wr::IdNamespace is unique only within same WebRender instance. Therefore different Window(WebRender) could assign same wr::IdNamespace.
Current Tab move assume that WebRenderBridgeChild::RecvWrUpdated() and WebRenderBridgeParent::UpdateWebRender() receive different wr::IdNamespace during Tab move. It causes accidental resource updates in WebRender.
There are two choices to address the problem. -  Change Gecko as to resist same wr::IdNamespace reuse during Tab move. For example, we could add generation id to recognize wr::WebRenderAPI change. -  Change webrender to assign unique wr::IdNamespace even between different webrender instances.
This sounds like a possible source of confusing bugs, so we should deal with it.
Priority: -- → P2
Whiteboard: [wr-mvp] [triage] → [wr-mvp]
Assignee: nobody → hshih
Status: NEW → ASSIGNED
https://github.com/servo/webrender/pull/1882 was merged.
The https://github.com/servo/webrender/pull/1882 is merged in gecko.
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.