Open Bug 1487393 Opened 7 years ago Updated 1 year ago

Firefox fails to upload a texImage2D to the GPU in WebGL with Samsung s7

Categories

(Core :: Graphics: CanvasWebGL, defect, P2)

60 Branch
defect

Tracking

()

People

(Reporter: petter.gasstrom, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180807170231 Steps to reproduce: Loaded a glb model with A-Frame in ThreeJS. This scene specifically: https://codepen.io/staphan/pen/vzyrzL?editors=1000 Device details: Samsung s7 SM-G930F. Android 8. latest firmware.Samsung Experience 9. Tested in Firefox Beta and plain version. Actual results: Gltf (glb) model does not show up at all. Got the following error messages with WebIDE: THREE.WebGLRenderer: EXT_texture_filter_anisotropic extension not supported. three.js:20144:5 Error: WebGL warning: texImage2D: Unexpected error during upload: 0x0502 Expected results: The model should be loaded and shown. This device (Samsung 7) apparently doesn't support anisotropic filtering. Google Chrome on the same device shows the models just fine. Apparently Firefox isn't able to correctly handle texImage2D GPU upload if expected anisotropic filtering settings aren't supported by the device. I assume that the same failure would happen on all devices that don't support anisotropic filtering.
Hello Petter, I will close the https://bugzilla.mozilla.org/show_bug.cgi?id=1487392 issue you submitted 3 minutes earlier than this one, you want this one to remain, right? I can see that you edited few things. Also, note that if you wanna correct something from the description you can add comments and mention what you change/add, there is no need to add another same issue. Thanks, Andrei
Flags: needinfo?(petter.gasstrom)
Thanks. I think the browser froze and threw me to the wrong page.
Flags: needinfo?(petter.gasstrom)
Hello, I was able to reproduce this issue on the following devices: Samsung Galaxy S7 (Android 7.0), Samsung Galaxy S8+ (Android 8) on the latest Nightly build. On an Sony Xperia Z5 (Android 7.0) the image was displayed completely. Can you please add an picture from your device with this issue? Those are the pictures from my devices: https://drive.google.com/file/d/1fBkv-r6T6w_W6rGai7Xy3WuEeROWbrqS/view - Samsung Galaxy S8+ Android 8.0.0 https://drive.google.com/file/d/1EXAZmcWO3Af6O8M9nepxG5_ZoUX3miRA/view - Sony Xperia Z5 - Android 7.0 Thanks, Andrei
Flags: needinfo?(petter.gasstrom)
The screen looks exactly like your Samsung S8 screen. I was also able to replicate the bug with a HUAWEI Mate 10 Pro.
Flags: needinfo?(petter.gasstrom)
I was able to isolate the issue to material settings. When I used a collada model with an unlit material with a diffuse texture and it rendered correctly, but a collada material with a normal map for instance fails texImage2D upload. How long does it usually take to get a dev to look at a bug? This one is definitely confirmed.
It's definitely the shader used. I removed all textures except the diffuse and the issue persists.
Hello Petter, Thank you for your fast response, as I said in Comment 4 and your Comment 5 I will set this issue as New. Thanks, Andrei
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: General → Graphics
Product: Firefox for Android → Core
Component: Graphics → Canvas: WebGL
Flags: needinfo?(jgilbert)
Priority: -- → P3
Whiteboard: [gfx-noted]

#define GL_INVALID_OPERATION 0x0502
Weird!

Flags: needinfo?(jgilbert)
Priority: P3 → P2
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.