AnsweredAssumed Answered

WebGL rendering errors in Google Chrome

Question asked by r.koenigmysynergis-esridist Employee on Sep 5, 2019
Latest reply on Sep 12, 2019 by MGeorge-esristaff

We are sporadically experiencing WebGL rendering issues on one of our development computers in Google Chrome.

The whole screen switches to black for a few seconds and after that the Google Chrome (newest version 76) displays an emtpy map. We are using a 2D MapView, layer types are MapImageLayer, FeatureLayer and VectorTileLayer.


We are using JS API 4.11.

Until now we couldn't find any relation between the displayed layers and the error occuring. 


I just wanted to ask if anyone else has experienced something like this and maybe has hints for pinning down the issue.


Google Chrome dev tools shows an error:

requestAnimationFrame (async)
f @ dojo.js:formatted:11387
h @ dojo.js:formatted:11359
l @ dojo.js:formatted:11354
requestAnimationFrame (async)
f @ dojo.js:formatted:11387
h @ dojo.js:formatted:11359
l @ dojo.js:formatted:11354
VM1907:103 Uncaught TypeError: Failed to execute 'shaderSource' on 'WebGLRenderingContext': parameter 1 is not of type 'WebGLShader'.
at a._loadShader (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:103:238)
at a.initialize (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:93:457)
at a.bindProgram (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:647:240)
at q._drawFill (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:133:20)
at q.render (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:127:371)
at p._renderFill (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:105:215)
at p.renderBucket (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:99:20)
at h.doRender (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:73:163)
at p.hitTest (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:103:301)
at h._hitTest (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:87:191)
a._loadShader @ VM1907:103
a.initialize @ VM1907:93
a.bindProgram @ VM1907:647
q._drawFill @ VM2007:133
q.render @ VM2007:127
p._renderFill @ VM2007:105
p.renderBucket @ VM2007:99
h.doRender @ VM2007:73
p.hitTest @ VM2007:103
h._hitTest @ VM2007:87


After restarting the browser everything works fine again using the same code and layers, so the problem seems not to be directly related to our application.