i use both iphone and samsung and they both have different bugs when playing mcoc. iphone seems to have the worst bugs that literally ruin aw, aq, and cause more deaths overall in my experience. with samsung there is a pause in ever fight but it doesnt happen more than once per fight. not sure if thats good or bad lol
I play on an iPad and the problem I was getting was a consistent crash after about 30 minutes. It got to the point where I always restarted the game before AW fights.
I'm on the X and luckily I haven't had too many major issues. The only thing I've noticed is that when I turn my phone off and turn it back on and click resume fight, I have to hold block about a half a second early to be able to parry and there is insane lag. I feel bad for all the people who experience this regularly.
Updated the game but nothing changed so I tried something new. I logged out from my accounts (Google play/Kabam) and logged back in with only Kabam id and somehow game feels smoother and I can play pretty long time without memory leak issues. Weird...
I play on an iPad and the problem I was getting was a consistent crash after about 30 minutes. It got to the point where I always restarted the game before AW fights.
That problem has gone.
This is exactly my issue, but it has not gone away or even improved since it began many months ago. Each update I hope it's at least a little better, but it's not. I have to restart every 20-30 mins or so and before I do any AW or AQ fights. I can usually tell when the crash is going to happen because the game starts to get laggy. I restart and it's fine for another 20-30 mins. Playing on a 2 year old iPad.
I said that logging in with only Kabam ID decreased memory leak issue but nope, today played arenas and again after 30 min of gameplay menus are laggy. I think fix will come when Kabam gonna create their own game engine.
I said that logging in with only Kabam ID decreased memory leak issue but nope, today played arenas and again after 30 min of gameplay menus are laggy. I think fix will come when Kabam gonna create their own game engine.
I’ve tried the suggestions made by @DNA3000 above. Turning off all notifications helps a little, although I continue to have frame drop issues with more noded, interaction-heavy content (for example, 7.3).
Luckily, the team has been so generous with solo potions I had a ton to fall back on when I experienced those issues…
My iPhone 8 is still experiencing the memory leak issue. Game get slower as I do more fights. If I don’t restart the game, it will crash. Like this morning, I used up my energy in eq and too lazy to restart for aq even though I noticed the slowness. Guess what, the game **** out in my 3rd fight in AQ.
If we are taking about the same thing—stuttering, frame drop—then it isn’t just an android issue. I experience it on iOS and have for most of the past few months. When I play for more than 15-20 minutes consecutively, it is pretty reliable.
Either that or I am involuntarily shaking and having brief episodes of syncope while I play.
Dr. Zola
Again, I will ask the disagrees above—provide commentary. Spamming a reaction resolves nothing. Is it resolved for you on Android, iOS, etc.
What device do you use? I have a 12 and an 8, neither of those have issues
Wth, I play on 12 and 8 and both have terrible issues 🤷🏽♂️
I said that logging in with only Kabam ID decreased memory leak issue but nope, today played arenas and again after 30 min of gameplay menus are laggy. I think fix will come when Kabam gonna create their own game engine.
I... don't know where you heard that. We're not building our own game engine. We're refactoring our input system, which may be what's being confused for a new game engine.
When you have these kinds of issues, can you please be sure to report them to our Support team? We're doing our best to fix these issues but can't do it if we don't know about it. While some bugs might look the same on the outside (eg. Laggy menus or a stutter), the underlying cause is not always the same.
If we are taking about the same thing—stuttering, frame drop—then it isn’t just an android issue. I experience it on iOS and have for most of the past few months. When I play for more than 15-20 minutes consecutively, it is pretty reliable.
Either that or I am involuntarily shaking and having brief episodes of syncope while I play.
Dr. Zola
Again, I will ask the disagrees above—provide commentary. Spamming a reaction resolves nothing. Is it resolved for you on Android, iOS, etc.
What device do you use? I have a 12 and an 8, neither of those have issues
Wth, I play on 12 and 8 and both have terrible issues 🤷🏽♂️
wouldn't that mean it HAS to be an issue with your connection? what other explanation is possible?
I said that logging in with only Kabam ID decreased memory leak issue but nope, today played arenas and again after 30 min of gameplay menus are laggy. I think fix will come when Kabam gonna create their own game engine.
I... don't know where you heard that. We're not building our own game engine. We're refactoring our input system, which may be what's being confused for a new game engine.
When you have these kinds of issues, can you please be sure to report them to our Support team? We're doing our best to fix these issues but can't do it if we don't know about it. While some bugs might look the same on the outside (eg. Laggy menus or a stutter), the underlying cause is not always the same.
Thanks for commenting on this thread. It’s an ongoing issue for me and a perplexing one. I wish I knew what to do to resolve it—some of what @DNA3000 suggested helped a little, but I’ve run into it again today and yesterday.
I’m happy to share my experience in a Bugs thread if there’s one that’s appropriate.
I said that logging in with only Kabam ID decreased memory leak issue but nope, today played arenas and again after 30 min of gameplay menus are laggy. I think fix will come when Kabam gonna create their own game engine.
I... don't know where you heard that. We're not building our own game engine. We're refactoring our input system, which may be what's being confused for a new game engine.
When you have these kinds of issues, can you please be sure to report them to our Support team? We're doing our best to fix these issues but can't do it if we don't know about it. While some bugs might look the same on the outside (eg. Laggy menus or a stutter), the underlying cause is not always the same.
Thanks for comment! I already reported about these issues in Bugs thread. P.S. most likely I heard about Kabam game engine in forums/YouTube.
If we are taking about the same thing—stuttering, frame drop—then it isn’t just an android issue. I experience it on iOS and have for most of the past few months. When I play for more than 15-20 minutes consecutively, it is pretty reliable.
Either that or I am involuntarily shaking and having brief episodes of syncope while I play.
Dr. Zola
Again, I will ask the disagrees above—provide commentary. Spamming a reaction resolves nothing. Is it resolved for you on Android, iOS, etc.
What device do you use? I have a 12 and an 8, neither of those have issues
Wth, I play on 12 and 8 and both have terrible issues 🤷🏽♂️
wouldn't that mean it HAS to be an issue with your connection? what other explanation is possible?
Actually, bad connections can only cause certain kinds of problems. Your internet connection can completely disappear and combat itself is ordinarily not affected (at least right up to the point where you're completely disconnected), so a slow connection obviously cannot hurt more than that.
Actual fights (as opposed to navigating around the game's menus and maps) require server connectivity to initialize them, and there's some keep alive stuff that gets ping ponged between the game client and the game servers, but a slow connection doesn't usually cause fight lag. A lag or studder *during* a fight is explicitly symptomatic of one simple thing that disguises a lot of complex things: the phone is doing something else. And whatever it is, it causes a noticeable disruption in game play.
The reason why memory leaks *can* (but do not always) cause game lag or stuttering is because when memory gets low or fragmented or both, such as if the game client is leaking memory, you could run into swapping or loading or garbage collection, all of which can noticeably pause game play or cause it to freeze momentarily, sometimes multiple times. Eventually the leak causes free memory to drop to a critical level and the game client crashes. But on its way down, it can sometimes exhibit stuttering or freezing.
Why this is different for different players even running the same device is due to the fact that no two people's memory maps are identical. No two people run the same set of apps, doing the same things, using memory in the same way. And these kinds of problems are not just about how much memory is used and unused. Two devices could both have the exact same amount of free memory but if one of them is experiencing more memory fragmentation they will likely exhibit worse performance.
(For those not aware of the technicalities of memory fragmentation, it is like Tetris. If we're both playing Tetris and you count the white space on my board and your board and find the number to be equal, that doesn't mean we're in the same situation. You could have your white space organized well, while mine could be scattered in a lot of disjoined holes. That would make it harder for me to find space to drop a piece than you. Memory usage is like that: memory is used, then freed, then reused. If you use memory in tiny pockets and randomly free them you could end up with lots of tiny spaces surrounded by used memory. It is now harder to find space for big things.)
Incidentally, memory management is one of the Really Big Things that often causes apps to run better on iOS than Android. It isn't that iOS has a better memory management system, it is that Apple only has to support a couple dozen devices at any moment in time, and app developers only have to test and optimize on a similar number. Android developers have to test and optimize for hundreds of platforms, each one of which has its own set of quirks.
A PC typically contains 16GB or more these days. A PS4 contains 8GB. Most phones contain 2 or 3 GB of RAM. But they are being asked to do similar things. If your app runs out of memory on a PC these days you're probably an idiot. But it takes some effort to squeeze a game into the footprint of a PS4, and it takes extreme effort between the OS vendor, the software development tools, and the app developer, to make a game fit in 2GB. While everything else is running on the phone at the same time. Very tiny platform or device quirks can significantly change how memory starved applications run on a device.
Playing iPad mini4 on airplane mode and notification off improved the game time from 30 minutes to 1,5hour. Dunno why, but it’s still not reliable as it still crash, but an improvement from my part nonetheless.
@DNA3000 maybe force closing some apps will improve something? Reduce this memory leak?
It can to some degree, but only up to a point. It will not reduce the actual memory leak, but it will make more memory available. The problem is that memory leaks will eventually fill up any memory you release, In testing I found that a cleanly rebooted phone lasted longer before crashing than one that had been running for a while. But like on the order of 5-10% longer. What helped more was avoiding doing things that required a lot of resources.
This is not the sort of advice you can just give to anyone, but let's say you're grinding the arena. The way I grind arena is generally to use my champs from top to bottom. I don't scroll around or skip around forming teams, and my sort order allows me to go from top to bottom. But what if you don't do that, and you scroll around a lot? You'll probably crash faster, because all that scrolling around requires the game client to swap into active memory the profile pictures of all the champs you're seeing. In testing I was able to get the client to crash *faster* by doing just that.
That's also why I suggested disabling notifications: every time the phone gets a push notification it has to "wake up" the app it is for, and swap some stuff into active memory to process that notification before going back to sleep. All of that use-memory free-memory use-memory free-memory probably contributes to memory fragmentation, which aggravates the MCOC memory leak. It can also be the straw that breaks the camel's back, if you're trying to process notifications while memory available spirals lower and lower.
One thing I have noticed recently is that whenever a special attack is about to be thrown, there is a slight lag which can mess me up when dealing with an Sp that is difficult to dex. This mostly happens when the defender throws an Sp. It doesn't happen as often when I throw my Sps
Just an example that this memory leak need The highest priority. This kind of lagging really underperformance me in war and in other places.
Holy cow! Tell me that’s just the video recording doing that. If not, I have no idea how you play the game.
The pause at the 52 second mark I experienced today. Fight just stopped, dead frozen, for a couple of seconds.
But my lags aren’t nearly as pervasive as yours.
Dr. Zola
It’s exactly like this even if not recording. Restart app, clean cache and other various tips doesn’t really work. The error is on kabam’s side with this memory leak issue. This is actually very important if we are gonna do season wars and so and especially more important if kabam want to continue with this summoner showdown tournament thing then the performance has to be on top.
I've noticed this issue more frequently on my 2019 iOS Apple iPad Mini more than my Android Google Pixel 4 XL.
However, in all fairness I tend to prefer to play on the iPad more often than the phone. (Bigger screen, faster loading times, etc)
Generally it occurs when I have been playing for more than 30 minutes, and especially worse if I switch between game modes (EQ, AQ, AW, arena, etc)
A rule of thumb I have been doing so I would stop losing attack bonuses, and half health in AQ is force close everything, reboot iPad, then go in fresh and immediately go into war or AQ to attack to ensure the game doesnt randomly close on me.
Just an example that this memory leak need The highest priority. This kind of lagging really underperformance me in war and in other places.
If what I'm seeing in the recording is exactly what you're experiencing in the game, that doesn't look to me like a pure game client issue. The only time I saw that kind of behavior was when we were having those horrible overheating issues when the game client itself might have been at fault, but the issue wasn't that the game client itself was doing things badly, the game client was overheating the phone to the point that the phone's thermal throttle protections were being engaged to prevent meltdown, which caused the entire phone to slow down in bursts.
Is your phone running very hot when you're playing? Have you tried playing without a case (which can sometimes exacerbate heating)? Does the game seem to run fine initially, then get progressively worse even after rebooting (rebooting doesn't cool the phone down on its own much, so while reboots generally fix most game client problems temporarily they do nothing for overheating issues).
@DNA3000 Phone isn't overheating for me(barely warm). After restarting game it's running smooth as butter. Well, I don't have issues with gameplay but only with slow/laggy menus. As someone said before game becomes slower after every single fight. Loading times increases and menus animations lags a lot. I can play Marvel Future Revolution till battery runs out without any problems.
@DNA3000 Phone isn't overheating for me(barely warm). After restarting game it's running smooth as butter. Well, I don't have issues with gameplay but only with slow/laggy menus. As someone said before game becomes slower after every single fight. Loading times increases and menus animations lags a lot. I can play Marvel Future Revolution till battery runs out without any problems.
Slow or laggy menus might be resource swapping. What I saw in the video went way beyond that though, which is why I wondered if thermal throttling might be a culprit.
Just an example that this memory leak need The highest priority. This kind of lagging really underperformance me in war and in other places.
If what I'm seeing in the recording is exactly what you're experiencing in the game, that doesn't look to me like a pure game client issue. The only time I saw that kind of behavior was when we were having those horrible overheating issues when the game client itself might have been at fault, but the issue wasn't that the game client itself was doing things badly, the game client was overheating the phone to the point that the phone's thermal throttle protections were being engaged to prevent meltdown, which caused the entire phone to slow down in bursts.
Is your phone running very hot when you're playing? Have you tried playing without a case (which can sometimes exacerbate heating)? Does the game seem to run fine initially, then get progressively worse even after rebooting (rebooting doesn't cool the phone down on its own much, so while reboots generally fix most game client problems temporarily they do nothing for overheating issues).
It wasn’t even warm since this war fight happened after I came home from gym and the phone don’t have any cellular signal built in it, but only WiFi signal so it stayed home during my training pass so the phone was cold.
Comments
iphone seems to have the worst bugs that literally ruin aw, aq, and cause more deaths overall in my experience.
with samsung there is a pause in ever fight but it doesnt happen more than once per fight. not sure if thats good or bad lol
It got to the point where I always restarted the game before AW fights.
That problem has gone.
Luckily, the team has been so generous with solo potions I had a ton to fall back on when I experienced those issues…
Dr. Zola
When you have these kinds of issues, can you please be sure to report them to our Support team? We're doing our best to fix these issues but can't do it if we don't know about it. While some bugs might look the same on the outside (eg. Laggy menus or a stutter), the underlying cause is not always the same.
I’m happy to share my experience in a Bugs thread if there’s one that’s appropriate.
Dr. Zola
P.S. most likely I heard about Kabam game engine in forums/YouTube.
Actual fights (as opposed to navigating around the game's menus and maps) require server connectivity to initialize them, and there's some keep alive stuff that gets ping ponged between the game client and the game servers, but a slow connection doesn't usually cause fight lag. A lag or studder *during* a fight is explicitly symptomatic of one simple thing that disguises a lot of complex things: the phone is doing something else. And whatever it is, it causes a noticeable disruption in game play.
The reason why memory leaks *can* (but do not always) cause game lag or stuttering is because when memory gets low or fragmented or both, such as if the game client is leaking memory, you could run into swapping or loading or garbage collection, all of which can noticeably pause game play or cause it to freeze momentarily, sometimes multiple times. Eventually the leak causes free memory to drop to a critical level and the game client crashes. But on its way down, it can sometimes exhibit stuttering or freezing.
Why this is different for different players even running the same device is due to the fact that no two people's memory maps are identical. No two people run the same set of apps, doing the same things, using memory in the same way. And these kinds of problems are not just about how much memory is used and unused. Two devices could both have the exact same amount of free memory but if one of them is experiencing more memory fragmentation they will likely exhibit worse performance.
(For those not aware of the technicalities of memory fragmentation, it is like Tetris. If we're both playing Tetris and you count the white space on my board and your board and find the number to be equal, that doesn't mean we're in the same situation. You could have your white space organized well, while mine could be scattered in a lot of disjoined holes. That would make it harder for me to find space to drop a piece than you. Memory usage is like that: memory is used, then freed, then reused. If you use memory in tiny pockets and randomly free them you could end up with lots of tiny spaces surrounded by used memory. It is now harder to find space for big things.)
Incidentally, memory management is one of the Really Big Things that often causes apps to run better on iOS than Android. It isn't that iOS has a better memory management system, it is that Apple only has to support a couple dozen devices at any moment in time, and app developers only have to test and optimize on a similar number. Android developers have to test and optimize for hundreds of platforms, each one of which has its own set of quirks.
A PC typically contains 16GB or more these days. A PS4 contains 8GB. Most phones contain 2 or 3 GB of RAM. But they are being asked to do similar things. If your app runs out of memory on a PC these days you're probably an idiot. But it takes some effort to squeeze a game into the footprint of a PS4, and it takes extreme effort between the OS vendor, the software development tools, and the app developer, to make a game fit in 2GB. While everything else is running on the phone at the same time. Very tiny platform or device quirks can significantly change how memory starved applications run on a device.
This is not the sort of advice you can just give to anyone, but let's say you're grinding the arena. The way I grind arena is generally to use my champs from top to bottom. I don't scroll around or skip around forming teams, and my sort order allows me to go from top to bottom. But what if you don't do that, and you scroll around a lot? You'll probably crash faster, because all that scrolling around requires the game client to swap into active memory the profile pictures of all the champs you're seeing. In testing I was able to get the client to crash *faster* by doing just that.
That's also why I suggested disabling notifications: every time the phone gets a push notification it has to "wake up" the app it is for, and swap some stuff into active memory to process that notification before going back to sleep. All of that use-memory free-memory use-memory free-memory probably contributes to memory fragmentation, which aggravates the MCOC memory leak. It can also be the straw that breaks the camel's back, if you're trying to process notifications while memory available spirals lower and lower.
Just an example that this memory leak need The highest priority. This kind of lagging really underperformance me in war and in other places.
The pause at the 52 second mark I experienced today. Fight just stopped, dead frozen, for a couple of seconds.
But my lags aren’t nearly as pervasive as yours.
Dr. Zola
You’re welcome.
However, in all fairness I tend to prefer to play on the iPad more often than the phone. (Bigger screen, faster loading times, etc)
Generally it occurs when I have been playing for more than 30 minutes, and especially worse if I switch between game modes (EQ, AQ, AW, arena, etc)
A rule of thumb I have been doing so I would stop losing attack bonuses, and half health in AQ is force close everything, reboot iPad, then go in fresh and immediately go into war or AQ to attack to ensure the game doesnt randomly close on me.
Is your phone running very hot when you're playing? Have you tried playing without a case (which can sometimes exacerbate heating)? Does the game seem to run fine initially, then get progressively worse even after rebooting (rebooting doesn't cool the phone down on its own much, so while reboots generally fix most game client problems temporarily they do nothing for overheating issues).