Globe failing to render in Firefox mobile 68 on Samsung devices

[OliverColeman]

The globe is failing to render in Firefox mobile version 68 (latest) on at least two different Samsung mobile phones (Galaxy A5 with Android 7.2 and Galaxy Note 8 with Android 9.0)

Example: demo at https://cesiumjs.org

Browser: Firefox mobile 68

Operating System: Android 7.2 and 9.0

[mramato]

Can someone else with Android test this out to see if it's device specific or Firefox specific? My guess is that it's a problem with all Firefox mobile Android installs, but we should confirm.

@OliverColeman Does Cesium work on these phones when using Chrome?

[OmarShehata]

I can see the same issue, nothing is rendered in the canvas on the cesiumjs.org demo or on Sandcastle on my Pixel 3 in Firefox. CesiumJS works fine on Chrome in the same device.

There's no errors in the console or failed requests, but there are a lot of WebGL warnings (which I can see by doing remote debugging off of my phone):

Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: checkFramebufferStatus: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 4 Cesium.js:121159:39
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: drawElements: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175211:29
Error: WebGL warning: drawElements: Framebuffer must be complete. Cesium.js:175211:29
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6 Cesium.js:175164:12
Error: WebGL warning: clear: Framebuffer must be complete. Cesium.js:175164:12
Error: WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) Cesium.js:175164:12
Source map error: request failed with status 404
Resource URL: https://cesiumjs.org/Cesium/Build/CesiumUnminified/Cesium.js
Source Map URL: protobuf.js.map

[mramato]

@OmarShehata It would be interesting to compare webglreport results from Firefox vs Chrome on your machine. This could also be a straight-up FF mobile bug. Do other WebGL renderers/demos work?

[OmarShehata]

Most of the examples on threejs.org work fine, but a few generate the exact same warnings as above and don't render anything, such as:

• Fire
• Birds

This is the closest Firefox bug I've found: https://bugzilla.mozilla.org/show_bug.cgi?id=1281181. I think the next step would be turning off a few things in the CesiumJS context (like the depth texture extension etc. https://github.com/AnalyticalGraphicsInc/cesium/blob/a1565d97a0332df8d4db8994d3d9ac20b306cc6e/Source/Renderer/Context.js#L277-L291) and try to narrow down what's causing it.

Chrome on Pixel 3:

Firefox on Pixel 3:

[mramato]

@OmarShehata sounds like a reasonable approach. If we find a busted/faulty extension, we can put in a FF mobile specific check to not use it until we know it's fixed. (Or a best case scenario is we figure out an issue somewhere in our own code that we can just fix).

[mramato]

I would also encourage someone who can reproduce this to open up a Firefox bug and link to it from here.

[MuhammedKalkan]

@ www.terrainserver.com, i am using 1.61. Strangely only on android device (using chrome) globe fails to render at specific distance. When you get close, it renders as usual. Iphone safari and chrome is stable. Also desktop is stable

[OmarShehata]

@Nymria that sounds like the same issue as #7871.

If you turn off globe lighting it should fix that. If so, I think this is different from this issue where nothing is rendered at all.