same here, this is getting horrible since last game update (12/07/18).

when it happen in firefox, close the browser... and start firefox again...

happen more often on 32 bit version of browser that on 64 bit version of browser... for know what version of browser you use with firefox, click "Help" and then "over  Firefox"...

for the tech people, a quote who somehow explain why it happen : " This is not the bitness of the operating system that matters, but the bitness of the browser that the user is using. For example, many users still run 32-bit Firefox on a 64-bit system, which means that the theoretical maximum memory available for the browser process is 4GB. Note that the heap memory should also be continuous, while allocation/deallocation of big chunks can eventually make this memory fragmented. So even though there might be lot of free memory available for the browser process within those theoretical 4GB, there might still be no continuous block of enough size. The problem often occurs when the game tab is reloaded multiple times."

in short, if you refresh often with a 32 browser, you will hit these "web gl out of memory fast"... from time to time, close the browser and open it again...

Having several tab open increase the issue too... tab use the same process... better to have a several windows that tab since windows are a own process who can address 4gb memory each in 32 bit browser on 64 bit OS... open firefox 32 bit one time for viking only, open a second firefox 32 bit for the other things ...

same with 64 bit firefox, issue will happen after a very long time ( days with browser running ) since the garbage collector in unity will create memory fragmentation with time

for the tech people, a quote who somehow explain why it happen : " This is not the bitness of the operating system that matters, but the bitness of the browser that the user is using. For example, many users still run 32-bit Firefox on a 64-bit system, which means that the theoretical maximum memory available for the browser process is 4GB. Note that the heap memory should also be continuous, while allocation/deallocation of big chunks can eventually make this memory fragmented. So even though there might be lot of free memory available for the browser process within those theoretical 4GB, there might still be no continuous block of enough size. The problem often occurs when the game tab is reloaded multiple times."

I have got that also ... only on my computer that did the recent window update and only with opera and Vivaldi browsers.  Maybe try a different browser.

This is NOT a player based issue.

most of the time, you have the webgl error when the memory used by your browser is a little above 1.8 gb...


on player side, clear cache at end of session change nothing... but there is a few thing who can help... try to keep your browser to use the less memory is possible when you start it... by example, setup all your plug-in on "ask for start"

anesfan said:

[…]

if i can do it on a 10 year old computer with xp, every computer can do it

[…]

so, work can be done on both side for improve the game experience but increase the memory reserved for unity opengl will only make the problem worse... was is needed is optimization on both side

I have been using a 32-bit PC with a 1G GPU, 4G RAM and a Intel Core 2 processor for a long time. The game was slower in response to actions as clicking tasks etc. But I could run two profiles at once with no big disadvantage.

Now I am on a 64-bit system always running latest 64-bit browsers. 8G GPU RAM, 16G System RAM, high end M.2 OS disk etc.

I have a separate profile for Vikings in Firefox / Chrome etc. where I have few to no plugins / enable disable some on need.

Still: Memory faults are coming frequently. The worst thing is to scan kingdom. After some minutes of looking around the game always crashes due to memory fault.

Quite often there is also a lot of flickering in the game. For example looking at the event windows it is impossible to scroll them cause game keeps re-painting every 0.5 second or so. Same goes for invaders etc. This is usually toward the end of events, and has perhaps been improved by last update.

i am also on 64 bits firefox and win 10 64 bits.

game is crashing every fucking 20 min when i scan kingdom.

Thanks for all the suggestions..

I have done everything I can and now its in the hands of Plarium as I STILL have same issues..

Really hope they can make a good fix as it could cost me big if this happens just after I drop a shield to attack....