Closed
Bug 1869931
Opened 2 years ago
Closed 1 year ago
WebGPU rendering is not synchronized to dom
Categories
(Core :: Graphics: WebGPU, defect)
Core
Graphics: WebGPU
Tracking
()
RESOLVED
FIXED
124 Branch
| Tracking | Status | |
|---|---|---|
| firefox124 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro, NeedInfo)
References
Details
Attachments
(1 file)
WebGPU rendering needs to be synchronized to dom like WebGL and canvas 2D. But the current rendering is not synchronized to dom.
| Assignee | ||
Updated•2 years ago
|
Assignee: nobody → sotaro.ikeda.g
| Assignee | ||
Comment 1•2 years ago
•
|
||
If we want the synchronization of WebGPU, there are the followings
- [1] Use sync IPC with first rendering like WebGPU ClientWebGLContext::GetFrontBuffer()
- [2] Use wait for first rendering in RemoteTextureMap::GetRemoteTextureForDisplayList() that is going to be added by D194352 of Bug 1829026.
- [3] async wait at WebRenderAPI::HandleWrTransactionEvents() without sync IPC of [1]. It is going to be added at Bug 1863257.
[3] is ideal way to address the problem.
| Assignee | ||
Comment 2•2 years ago
|
||
It seems better to apply [2] at first as short term solution. It could simplify RemoteTextureMap handling.
| Assignee | ||
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Attachment #9370329 -
Attachment description: WIP: Bug 1869931 - Remote RemoteTexture push callback → WIP: Bug 1869931 - Remove RemoteTexture push callback
Comment 4•2 years ago
|
||
The severity field is not set for this bug.
:jimb, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(jimb)
Updated•1 year ago
|
Attachment #9370329 -
Attachment description: WIP: Bug 1869931 - Remove RemoteTexture push callback → Bug 1869931 - Remove RemoteTexture push callback
Pushed by sikeda.birchill@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0c3c8e5c4963
Remove RemoteTexture push callback r=gfx-reviewers,lsalzman
Comment 6•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox124:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 124 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•