Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

WebGL build problems in MS Edge

A topic by vendolis created Jun 02, 2022 Views: 126 Replies: 3
Viewing posts 1 to 3
Submitted

Hi,

I just wanted to write something since I found that I had a lot of WebGL problems (including in my own game) during the Jam. Part of it might come from the current edition of MS Edge (Chromium-based) and possibly other chromium-based browsers. Chrome itself seems to work well in full-screen mode. At least every time I had an issue and started chrome to test the game things were working much better. 

In some cases, I also had input issues in Edge, but not in Chrome. I have not tested Firefox on anything yet, but if you use Edge and have issues, try Chrome.

Vendolis

Submitted

For some reason I had the opposite issue, webgl games were stuttering badly in Chrome, but worked flawlessly in Edge. No idea what the reason could be.

Submitted

The stuttering happens after you play a bun of games. I assume that there are some bad memory leaks that affect the GPU. After testing about 20 games, I had to reboot my computer since even a normal Steam game would not work anymore .. had only frame rates of 1-2 FPS and 99% GPU utilization. .. Browser change did help for a little but then it was also with another browser.

I am wondering if the problems are related to 2021.3 games. At least mine is one, and another one where I looked at the code is one as well. 

Submitted

Here are 2 tricks to overcome the issues with bad memory allocation:

• Run the game in private mode. This ensure that, when you close the tab/client, all memory (which are allocated in a closed memory box) gets properly cleared from the system' memory. In the case of a game with a saving feature, you will not be able to save anything though unless the saving feature is connected to a server (which I doubt anyone had time to do it in 10 days). It won't help with issues about GPU though, but will help with issues with CPU and general memory allocation.

•When closing the browser after playing, open the task manage (CTRL + ALT + DEL) and check if it's still opened in the background and look at what is taking all the memory. There could be something that was launched to run element in the WebGL codes that doesn't close properly.

There are other ways,  but that's generally the 2 things anyone can do with ease.