Select to view content in your preferred language

A recent Edge Stable Channel release has broken our application on virtual machines. Would greatly appreciate advice on how to proceed.

448
4
Jump to solution
09-16-2024 12:22 PM
RyanMoser
Emerging Contributor

My team supports a web application which uses the JS SDK. On August 22nd, users on virtual machines ran by VMWare started experiencing failures. The failure happens like this:

  1. The page and map begin to load. You see the map and its layers almost render to completion.
  2. The entire screen turns black for about one second. When the screen returns, the container which hosts the map is a blank white space.

On top of this, there are some strange JavaScript errors that sometimes occur. For example, one was caused by the extent property of the mapView not instantiating. When a line of code which referenced this property was executed, an error was thrown. This happens only on virtual machines. 

We did some digging today and discovered this error was brought on by Microsoft Edge Stable Channel release 128.0.2739.42, which came out on August 22nd. All other versions after this one have the same issue. We reverted our Edge version back to 127.0.2651.105, which released a week prior, and these issues are not present. 

Is this a known issue, and is there any guidance on how to proceed? I'm not sure where to start with troubleshooting this. 

0 Kudos
1 Solution

Accepted Solutions
George_Thompson
Esri Notable Contributor

I would contact technical support on this issue. There may have been an issue with the Chromium update.

Can you test Microsoft Edge version 128.0.2739.54?

--- George T.

View solution in original post

4 Replies
George_Thompson
Esri Notable Contributor

I would contact technical support on this issue. There may have been an issue with the Chromium update.

Can you test Microsoft Edge version 128.0.2739.54?

--- George T.
RyanMoser
Emerging Contributor

Thank you, I will email them. 

Yes, we've confirmed that 128.0.2739.54 has this issue, as do 128.0.2739.63, 128.0.2739.67 and 128.0.2739.79. 

0 Kudos
AndyGup
Esri Regular Contributor

Hi @RyanMoser, disregard, it sounds like you did contact support.

0 Kudos
AndyGup
Esri Regular Contributor

Here's the KB article with info on the Chromium issue and the versions affected: https://support.esri.com/en-us/knowledge-base/defective-chromium-128-update-and-arcgis-maps-sdk-for-...

0 Kudos