If not, performing the steps below should help resolve this as well: In the meantime, as a workaround, if you switch your default browser to something other than Google Chrome or Microsoft Edge, then completely quit and restart the MS Teams application, this should help. That being said, I will open a ticket on your behalf with our Support team so that they can keep you in the loop on this issue. It appears as if what you're experiencing may, in fact, be related, a known issue that our Engineering team is continuing to investigate. Thanks for taking the time to provide those details! I already tried to put -ignore-gpu-blacklist in the Chrome shortcut (even if I understood this is for Windows XP, right?).So sorry for the issues here.For the moment all I can do is close all Chrome windows and restart it. I already tried to open a new Chrome window, it does not work.So I am going to make Chrome disable WebGL a lot of times, and I do not want to restart it everytime it disables WebGL.
I know how I could reduce the resources my app asks for, but actually I am exploring its limits for testing purposes.Chrome disables WebGL probably because it requires too many resources: I ask it to display 400,000 billboards on Cesium, for those who know what this is.When Chrome stops WebGL and gives you the following error (in a yellow banner on top of the screen): "Rats! WebGL hit a snag.", and reloading does not work (WebGL is still not re-enabled), is it possible to re-enable WebGL without restarting Chrome?
0 kommentar(er)
