**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Stop Intentionally Lagging The Game
Kennado
Posts: 991 ★★★
I can live with wonky AI. You don’t need to intentionally throttle the game with lag spikes in fights to encourage spending money on items, on top of that. That’s borderline criminal if you ask me.
An iPhone 14 max pro shouldn’t have lag issues yet Kabam continues to lie to us that these lag issues aren’t intentional.
An iPhone 14 max pro shouldn’t have lag issues yet Kabam continues to lie to us that these lag issues aren’t intentional.
14
Comments
For those unfamiliar with memory leak, it's when an app incorrectly manages memory allocations and doesn't release it, causing the slowdown of all apps.
Kabam doesn't even own the servers the game uses. Everything you've said is a ridiculous conspiracy theory and you have no evidence to back it up.
People are disagreeing with you because you don't understand what you're talking about and the thing you're blaming kabam of isn't even possible either. Take your L and move on.
So 1) is there a way for me to get rid of the lags?
And 2) if it’s an app that can alleviate this issue, does it go against TOS?
I appreciate any real advice to this issue. Thanks.
For ios just go to the apple store and search cache cleaner. Clearing your cache has nothing to do with modifying the game, it's just freeing up memory the game and other apps are using that slows everything.
For clarification baseline for this phone is 3.2 gb. I just opened the game and it's 3.9 and balloons to 4.8gb after a few fights. Not great.
Perhaps uninstalling and reinstalling the app each month will work? Idk. Anyone else have any ideas? I understand this isn’t Kabam’s fault, but I’m willing to try to fix this issue at least occasionally on my end and would like to know all avenues available to me. Thanks again @klobberintyme
This would take a very long time to explain, as it involves how memory is managed on mobile devices (and things are slightly different on iPhone and Android on top of this) but the game did have a pretty bad memory leak a couple years back, and most of them were fixed last year. I was one of the heavy testers characterizing and reporting those issues to Kabam.
A memory leak is when the game allocates memory for something, and then when it no longer needs that stuff it forgets to free the memory. The way this happens is all memory is referenced with pointers or handles to that memory. Sometimes a bug will cause a program to throw away the handle to the memory because the memory is no longer needed, but fails to first free up the memory it is pointing to. It is like throwing away the key to a safety deposit box you're using because you think you don't need it anymore. You can't open it every again, and you also forget you're still paying rent for it so the post office can't use it for anyone else. That box is "gone."
When that happens, the memory that the game lost track of can't be freed by the game anymore, and it can't be freed by the phone because the game hasn't said it is done with it. So eventually you use up too much memory and run into problems.
What you're seeing is a different issue. I'm more familiar with iOS but I think its similar on Android. When an app uses memory and then stops needing it, that memory isn't "returned" to the operating system. It is kept around to be reused by the app when it needs more memory. Sort of like memory recycling. For complex technical reasons it is possible for an app to ask for memory, use it, then put it into the pile to be reused, but then ask for new memory instead of reusing the old memory. Not often, but occasionally, and this means the amount of memory the app is using slowly rises.
The memory "cleaners" aren't actually freeing that memory. Instead they are doing something more complicated, and the simplest way I can explain it is that the OS "asks" the app if they really need all that memory *now* or if it is safe to take some of that memory and temporarily swap it out and use it for something else. The app is then supposed to decide what it needs right away and what it might not need for a while. Apps don't do this in real time for performance reasons, so it only happens when these things are requested.
Switching to a cleaner and running it can reduce the memory footprint of MCOC. However, especially on iOS, it can also cause MCOC to restart completely. That's because if you force MCOC to swap resources out to free that memory and then immediately go back to playing the game, if the game was in certain states when that was performed rather than try to regain access to everything again the game will just decide it is better to restart and reload everything.
I am simplifying this almost to the point of being gibberish, but the bottom line is that I haven't seen real memory leaks affecting game stability in a while, but there might be more work that needs to be done to improve memory management overall. Using things designed to "optimize" memory might improve things temporarily, but they can also cause the game to just restart, which players can also just do themselves. I also don't play on Android, so I can't speak to what the experience on those platforms has been like recently.