BUG
THIS ARTICLE WILL BE UPDATED AS NEW INFORMATION IS MADE AVAILABLE.
Resolution Update:
As of August 29th, 2024, this issue is resolved in Chrome version 128.0.6613.114 and Microsoft Edge version 128.0.2739.54 . If you are experiencing this issue please update to the latest version of Chrome or Edge.
On August 20th, 2024 Chromium 128 was released to users. This update contains a defect that causes applications built with the ArcGIS Maps SDK for JavaScript to experience the following error Uncaught TypeError: Failed to execute 'uniform4fv' on 'WebGLRenderingContext': The provided float value is non-finite. on certain 3D apps.
This has been seen in ArcGIS Online and ArcGIS Enterprise (10.9.x and newer). It affects 3D applications like the SceneViewer.
Affected browsers: Edge - Version 128.0.2739.42 & Google Chrome - Version 128.0.6613.85
Update: Google Chrome released update 128.0.6613.113/.114 which resolves this issue on August 28th. Updating to this version is recommended. The release date for Edge has not yet been provided.
Chromium was made aware of this defect on August 24th, 2024 and the following issue was raised: Incorrect bindings for Float32List
Subsequently, BUG-000170285: Chromium 128 update causing WebGL error in web applications, Uncaught TypeError: Failed to execute 'uniform4fv' on 'WebGLRenderingContext': The provided float value is non-finite, was created to understand the impact this has had on Esri customers.
The public Knowledgebase article can be found here: Defective Chromium 128 update and ArcGIS Maps SDK for JavaScript
If you receive a case relating to Scene viewer or Expereince builder displaying "Uncaught TypeError: Failed to execute 'uniform4fv' on 'WebGLRenderingContext': The provided float value is non-finite. error in the dev tools, please attatch the customer to BUG-000170285: Chromium 128 update causing WebGL error in web applications, Uncaught TypeError: Failed to execute 'uniform4fv' on 'WebGLRenderingContext': The provided float value is non-finite.
As of August 28th, Chromium have acknowledged the defect and are working on rolling it back: Incorrect bindings for Float32List #comment12
The Chromium fix is scheduled to go to chrome beta: Incorrect bindings for Float32List #comment19
Article ID: 000033497
Get help from ArcGIS experts
Download the Esri Support App