Last 10 cycles of https://www.vsynctester.com/gputest.html are very slow with remote canvas.
Categories
(Core :: Graphics: Canvas2D, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox86 | --- | wontfix |
firefox87 | --- | wontfix |
firefox88 | --- | wontfix |
firefox89 | --- | fixed |
People
(Reporter: bobowen, Assigned: bobowen)
References
Details
Attachments
(1 file)
This is because of this setting in webrender, which gets propagated to this check in TextureClient and fails because the canvas gets bigger than 8192.
So, it falls back to a software canvas, which I think then gets drawn into a recording one and is really slow.
The textures can actually be 16384 (I think) and the moz2D limit mentioned in the webrender setting is actually a max allocation of 500MB, which means we could allow (square) textures of up to 11180, assuming 4Bpp.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by bobowencode@gmail.com: https://hg.mozilla.org/integration/autoland/rev/8350638712cf Increase webrender max texture size to max allowed by Moz2D. r=nical
Comment 3•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Comment 4•3 years ago
|
||
The patch landed in nightly and beta is affected.
:bobowen, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 5•3 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #4)
The patch landed in nightly and beta is affected.
:bobowen, is this bug important enough to require an uplift?
If not please setstatus_beta
towontfix
.For more information, please visit auto_nag documentation.
Unfortunately, this has introduced a performance regression elsewhere, so I won't be uplifting yet.
Updated•3 years ago
|
Updated•3 years ago
|
Description
•