1609510 - Maps websites are throwing several errors during navigation

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect, P5)

Description

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Build ID: 20200115093807

The following map websites are throwing several errors during navigation:

• Open web console
• Go to https://maps.google.com/
• Wait for loading the page, and observe that several errors are triggering in web console.

Errors such as:
Error: WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. maps line 1255 > scriptElement:5005:296
Error: WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. maps line 1255 > scriptElement:5005:296
Error: WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow.

• In https://www.openstreetmap.org/#map=2/39.0/10.9
  loading page gives some other errors:

Source map error: Error: request failed with status 404 Resource URL: https://www.openstreetmap.org/assets/application-4934642fec473bcc983ced35b73efef8351ec964bb0a54a03db5f2b83f34b838.js Source Map URL: leaflet-src.js.map;

• In https://www.mapquest.com/
  error:
  Script from “https://dpm.demdex.net/demconf.jpg?et:ibs%7cdata:dpid=96678&dpuuid=7UTaAfD4wPtd” was blocked because of a disallowed MIME type (“image/gif”).

Expected: Maps Websites do not give errors during navigation.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Does this only happen with WebRender turned on?

Comment 2

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

Hi,
issue is happening with WebRender turned on and off.

Regards!

Comment 3

[Jeff Muizelaar [:jrmuizel]]

That suggests it's not a WebRender issue.

Otherwise my suggestion is the same as in bug 1609518. If the user observable behaviour of the webpage is different in Firefox then Chrome and you believe the behaviour difference to be caused the error then you'll need to file bugs in the appropriate components for those errors. The error messages you've posted seem more like website issues than problems in Firefox.

Comment 4

[Jeronimo Torti (Please send NI request to Brindusa Tot)]

Hi,
I checked the pages on Chrome and I was able to reproduce the errors. Since this bug is not related to Firefox, I'll close it as Resolved - Works for me.

Thanks for the advise, regards!

Jerónimo.