topic Re: Map Error In New Chrome Update (128.0.6613.85) in ArcGIS Online Questions

Map Error In New Chrome Update (128.0.6613.85)

AaronBrake — Thu, 22 Aug 2024 15:16:31 GMT

Hi,

I'm a user of an application that uses ArcGIS, and with the new Chrome Update I'm seeing errors when I make a selection to view on the map.

The error I'm seeing is:

Uncaught TypeError: Failed to execute 'uniform4fv' on 'WebGLRenderingContext': The provided float value is non-finite.
at g.setUniform4fv (webgl.js:16:204)

It occurs about 50 times every time I try to make a new selection. The map now doesn't zoom in/pan to my selection anymore, but will just move a small amount while still making the selection.

Is there anything I can do to update, or is this a known issue?

Thanks in advance!

Re: Map Error In New Chrome Update (128.0.6613.85)

MathewCoyle — Thu, 22 Aug 2024 16:05:10 GMT

It may be related to the recent Chromium update. If so it requires an update on the ArcGIS Enterprise deployment.

https://support.esri.com/en-us/knowledge-base/impact-of-google-chrome-and-microsoft-edge-127-updates--000032813

If this application is entirely hosted on AGOL that shouldn't be the cause though. Do you have any other details on the application? Is it using custom widgets? Created in an older version of App Builder/Experience?

Re: Map Error In New Chrome Update (128.0.6613.85)

AaronBrake — Thu, 22 Aug 2024 16:24:37 GMT

I'm not super sure what the implementation of things is, I do know that the error is coming up in the javascript file hosted at: https://js.arcgis.com/4.18/esri/views/webgl.js

Further, I can say that it seems to be an update from today. I saw the usual behavior this morning but then after refreshing chrome from this update I started seeing this behavior.

Re: Map Error In New Chrome Update (128.0.6613.85)

MattNicol — Wed, 28 Aug 2024 14:05:27 GMT

Aaron and I work together - we were using the ArcGIS JavaScript API 4.18 when encountering this behavior. After updating to 4.30, it worked as expected again.

Edit: Be on the lookout for API changes too - depending on what version you started from and go to, other functionality might break without code updates. One example: The Identify process has breaking changes between 4.18 and 4.30.

Re: Map Error In New Chrome Update (128.0.6613.85)

DannyKing — Fri, 23 Aug 2024 18:59:27 GMT

We are using the ArcGIS JavaScript API 4.18 as well. If updating to 4.30 is not an immediate option, do you know of a way around this error? Is there a Chrome setting or flag to get around this? Will we have to tell our customers to not upgrade or downgrade their Chrome browser until we can deploy and update to their application with the latest API?

Re: Map Error In New Chrome Update (128.0.6613.85)

MattNicol — Fri, 23 Aug 2024 19:38:51 GMT

I'm not sure, unfortunately.

The rest of this is pure conjecture, so take it with a grain of salt. 😀

Given the original error, it seems like an interaction between how Chrome handles floating point values and the results of the math that the ArcGIS JavaScript API is doing.

The reference to a "non-finite" number could refer to something like a JavaScript Infinity or NaN. The previous version of Chrome probably just essentially ignored it before, but (probably correctly) breaks on it now.

Whatever that calculation involved was seemingly updated sometime after 4.18 such that the result is either not calculated in the first place or no longer returns the "non-finite" number.

That's all a long-winded way of me saying, unless there's a flag you can set in Chrome to change how it handles the "non-finite" number, updating the ArcGIS JS API version is likely the only realistic option.

Re: Map Error In New Chrome Update (128.0.6613.85)

MichaelVolz — Mon, 26 Aug 2024 14:56:26 GMT

Do you know what the lowest ArcGIS JavaScript API version that would resolve this issue?

My org has one web app at ArcGIS JavaScript API version 4.29 and this issue does not exist there. We have another web app at a different version I think (Not sure), where this exact issue is occurring.

Re: Map Error In New Chrome Update (128.0.6613.85)

MattNicol — Mon, 26 Aug 2024 14:59:56 GMT

I don't unfortunately - we jumped directly from 4.18 to 4.30. If you need the minimum version where this is fixed, I'd just keep incrementing the version number until you find where it works.

Re: Map Error In New Chrome Update (128.0.6613.85)

DevServiceTitan — Mon, 26 Aug 2024 15:59:06 GMT

4.20 seems to be the lowest version that resolves the issue

Re: Map Error In New Chrome Update (128.0.6613.85)

JonathanWilding — Tue, 27 Aug 2024 00:07:16 GMT

I was able to get my 4.13 app working again by downgrading to 4.11 after I noticed this same issue today.

Re: Map Error In New Chrome Update (128.0.6613.85)

maurenrivera — Tue, 27 Aug 2024 17:05:31 GMT

Jonathan, my app is using 4.11, but this issue papers. Do you know why? What's your Chrome's version?

Re: Map Error In New Chrome Update (128.0.6613.85)

maurenrivera — Tue, 27 Aug 2024 17:11:10 GMT

Jonathan, my app is using 4.11, but this issue papers. Do you know why? What's your Chrome's version?

Re: Map Error In New Chrome Update (128.0.6613.85)

ColinWerle1 — Tue, 27 Aug 2024 18:24:00 GMT

This is a great point. If application is in an ArcGIS Portal environment (10.8.1 - 11.2), you will want to ensure that you have the Portal for ArcGIS Application Display Patch (esri.com) installed. Note: As a best practice, clear the browser cache and re-launch the browser after installing the patch.

It may be a good idea to log a technical support case to continue looking into this as well, perhaps with the SDK team.

Re: Map Error In New Chrome Update (128.0.6613.85)

JonathanWilding — Tue, 27 Aug 2024 19:50:54 GMT

i have chrome: "Version 128.0.6613.85 (Official Build) (32-bit)", I just toggled back to 4.13 and the issue came back, then flopped back to 4.11 and it went away again.. I have spent most of the morning today updating and cleaning up a few of my applications to 4.30 but the rollback to 4.11 was a bit of a dirty quick fix and I don't advise it.

Re: Map Error In New Chrome Update (128.0.6613.85)

JonathanWilding — Tue, 27 Aug 2024 20:24:44 GMT

As an update, i found that the error" Failed to execute 'uniform4fv' on 'WebGLRenderingContext':" came up in a different spot in my test application so the roll back to 4.11 did not completely fix the issue it just moved it to a different spot.

Re: Map Error In New Chrome Update (128.0.6613.85)

DrewDowling — Tue, 27 Aug 2024 21:21:53 GMT

I just encountered this error on 3 apps running 4.14. 2 of them I upgraded to 4.20 and they are working now.

1 of them is using IdentifyTask class which is removed at 4.20. I downgraded to 4.11 as a quick and dirty fix and now this app is also working, at least so far. @JonathanWilding I'll update this thread if my users encounter the bug on the 4.11 app.

Re: Map Error In New Chrome Update (128.0.6613.85)

JonathanWilding — Tue, 27 Aug 2024 22:18:09 GMT

Hi @DrewDowling, If it helps, I presented itself when collecting the lat, long in 4.11 and 4.13:

view.on("click",function(event){

var lat = event.mapPoint.latitude

var long = event.mapPoint.longitude

var message = lat + " " + long

var latInput = document.getElementById("lat")

var lngInput = document.getElementById("lng")

latInput.innerHTML = lat

lngInput.innerHTML = long

})

Re: Map Error In New Chrome Update (128.0.6613.85)

MichaelVolz — Wed, 28 Aug 2024 13:58:29 GMT

So in the experience at my org, upgrading the javascript app to too high of a version created new issues after resolving the original issue seen at v4.18 (Maybe due to complexity of web app). I started at v4.26 with many new errors , then downgraded to v4.23 with less errors and finally to v4.21 that fixed the original issue yet did not create new errors in the web app.

Re: Map Error In New Chrome Update (128.0.6613.85)

MattNicol — Wed, 28 Aug 2024 14:04:55 GMT

Thanks for pointing this out - I updated my original answer to cover this.

Re: Map Error In New Chrome Update (128.0.6613.85)

seumoo — Wed, 28 Aug 2024 16:54:21 GMT

I'm on ArcGIS JS version 4.15 mainly using Edge and Chrome. Downgrading to 4.11 or upgrading to 4.20 did solve the interactivity issues with the map but broke core functionality like getting selected features. The WebGL issue is a known Chromium issue and it looks like it is currently being worked on: Chromium Issue #361823993

Using a non-Chromium browser seems to work with 4.15. I've notified my users to use a non-Chromium browser until a patch is released. Hopefully that will fix this issue.