Throttling Issue on Chrome
Not sure if anyone else has noticed, but if you play CasinoRPG in Chrome and go to a different tab, all of the game action freezes, and then you get some weird graphical things to happen when you bring the game's tab back to the foreground, especially in a slot game.
With Chrome 56 coming soon, this is going to be even worse, especially for timers, which may have very large effects on anything with a timer in it, and also any of the websocket features (chat, who enters your casino and where they go, etc.). http://blog.strml.net/2017/01/chrome-56-now-aggressively-throttles.html
Not sure if you're aware of this yet, or had any thoughts about what to do with it (I don't use websockets in my apps yet so I can't share anything helpful), but I do want to make sure you're able to keep such a great product going.
FlagDUDE08
shared this idea
-
FlagDUDE08
commented
I do know there is a BETA available for Chrome 56 if you want to try it out, but I also know how difficult it is for web programmers to change that environment for the purposes of a test. Hopefully things go well. :)
-
It is our understanding that this change won't further throttle pages that have an open WebSocket connection. We do all of our dev in Chrome, so this is certainly something we'll continue to watch.
