We have a few Web Mapping Applications that upon initial load have their basemaps and some layers disappear (the basemap layer turns white). The Esri loading circle then continues to circle without ever finishing loading.
The Web Mapping Application has several Hosted Feature Layers, but only a handful of simplified polygons are initially loaded in the map. We are leveraging a handful of bookmarks and filters. The maps that are in the web map applications were built with the Map Viewer Classic (we've tested, and it does not appear to make a difference which Map Viewer is used). We are on Enterprise version 10.9.1.
What makes this stranger is that they load fine in Firefox and Safari, but not in a Chromium browser (Edge, Chrome, Brave, etc).
When looking at DevTools, we see the following: WARNING: Too many active WebGL contexts. Oldest context will be lost.
We also see: Uncaught TypeError: Failed to execute 'shaderSource' on 'WebGLRenderingContext': parameter 1 is not of type 'WebGLShader'.
at p._loadShader (webglDeps.js:137:86)
at p.initialize (webglDeps.js:127:188)
at e.bindProgram (webglDeps.js:455:150)
at m.draw (webglDeps.js:328:99)
at webglDeps.js:1533:522
at Array.forEach (<anonymous>)
at f.doRender (webglDeps.js:1533:493)
at f._drawPhases (webglDeps.js:183:272)
at f._drawClippingRects (webglDeps.js:184:413)
at f.draw (webglDeps.js:179:140)
I have tried to change the basemap from a Vector Tile basemap to a raster basemap. Nothing changes.
The map has no issues loading in a map viewer.
