WebGL2 texSubImage2D generates invalid INVALID_OPERATION error
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
People
(Reporter: mozilla2, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.0.0 Safari/537.36
Steps to reproduce:
Ran this test
https://jsgist.org/?src=cce4c62ef5e85d4b84d738337add4b48
Actual results:
I created a texture using texStorage2D then tried to fill out all the mips manually and got an error on the last mip
Expected results:
No error
There's no error if I use texImage2D
instead
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:jgilbert, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•3 years ago
|
||
Ah, this is a test issue.
const maxLODs = Math.log2(maxTextureSize) | 0 + 1;
This is parsed as Math.log2(maxTextureSize) | (0 + 1)
, but I bet you meant (Math.log2(maxTextureSize) | 0) + 1
. Firefox and Chrome have different maxTextureSizes here:
- Firefox: 8192 (log2: 13)
- Chrome: 16384 (log2: 14)
Because one is even and the other odd, the ambiguous parse looks like it works fine on chrome, but the +1 might seem like it is dropped in Firefox.
"RESOLVED INVALID" is our "NOTABUG". Thanks for the report!
Description
•