Kronan
Viceroy
@estridI have had lots of memory problems lately with pages ending by 'Snap. Out of memory error.' or just going weird.
So I started to watch where the memory goes. When I opened the mini-game window to check the boat and city, chrome memory usage went up about 10% (of 8G). When I closed the mini-game, the memory usage did not go down. If all these minigames do that, they are taking lots of memory, because I play on 3 live servers too.
Absolutely correct.
The minigame engine is very computationally intensive (for animation effects AND linear programming modelling for the game itself...) for the client (PC, etc) , and it's costly to leave it running as the forward window, vs background. I have software tools that show this "drain" clearly...
If you leave it open overnight, your PC is grinding up electricity to just make heat. Fancy that, eh?
I don't leave the St. Patrick's Day Event minigame open for ANY duration once I'm done checking progress, or making an adjustment.
I also never leave FoE as my active window in my browser. When I'm done making city changes, collecting, or communicating (C,C,C,C), I bring any other browser tab/window forward (change focus) OR exit (close) the game until I need it again.
View the tool output:
A) Brave Browser and FoE as the open (forward) tab. Note the graphical usage - flat - and steady state for the time it was open.
B) Brave Browser and FoE as the open (forward) tab and the St. Patrick minigame open (including calculations and visual animations)
See the graph at the bottom, with the jump up in activity? That's when I opened the minigame, and left it open.
The name of the tool is CORE TEMP, and can be found with a google search. I've used it for years - and it's very reliable.
In my case, the tool shows all 8 threads of my Core I7 processor, and the temperatures, usage. etc.
Last edited: