MCPE-28469Please reduce MCPE's memory footprint on 512MB iPads so that it is usable again.
Some previous versions of MCPE have behaved very well on 512MB iPads, such as the iPad mini 1st Gen (which both my kids use), even when playing local multiplayer games for long periods of time. However, recent versions, including 1.2.3, have increased memory usage, which causes memory thrashing (which the kids observe as severe lagginess) and jetsam-triggered terminations of MCPE (which is obviously highly disappointing).
You can see from the JetsamEvent logs that are produced during these situations:
- "largestProcess" : "minecraftpe"
- "rpages" (resident pages) for minecraftpe around 65000-70000 pages, or 260-280 MB (32-bit iPads all use 4K pages).
- for the JetsamEvents in which minecraftpe is terminated by iOS, it will show "reason" : "vm-pageshortage"
If I launch MCPE on two iPad mini 1s, open a world in one, and join the game from the other, it will almost immediately jetsam the MCPE on the first iPad. But a short period of playing will also make it jetsam too.
In order to remedy this, it will be necessary to reduce the memory footprint on these devices. That optimisation may not be needed on 1GB and larger units.
You can query a device's total RAM by calling [NSProcessInfo processInfo].physicalMemory.
Please, have your QA team make it a standard practice to exercise 512MB iPads prior to release.
Linked Issues
Created Issue:
Please reduce MCPE's memory footprint on 512MB iPads so that it is usable again.
Some previous versions of MCPE have behaved very well on 512MB iPads, such as the iPad mini 1st Gen (which both my kids use), even when playing local multiplayer games for long periods of time. However, recent versions, including 1.2.3, have increased memory usage, which causes memory thrashing (which the kids observe as severe lagginess) and jetsam-triggered terminations of MCPE (which is obviously highly disappointing).
You can see from the JetsamEvent logs that are produced during these situations:
- "largestProcess" : "minecraftpe"
- "rpages" (resident pages) for minecraftpe around 65000-70000 pages, or 260-280 MB (32-bit iPads all use 4K pages).
- for the JetsamEvents in which minecraftpe is terminated by iOS, it will show "reason" : "vm-pageshortage"
If I launch MCPE on two iPad mini 1s, open a world in one, and join the game from the other, it will almost immediately jetsam the MCPE on the first iPad. But a short period of playing will also make it jetsam too.
In order to remedy this, it will be necessary to reduce the memory footprint on these devices. That optimisation may not be needed on 1GB and larger units.
You can query a device's total RAM by calling [NSProcessInfo processInfo].physicalMemory.
Please, have your QA team make it a standard practice to exercise 512MB iPads prior to release.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
duplicates
Crashes like these are automatically logged and sent to Mojang.
Regardless, the bug tracker is for bugs only, please direct all suggestions to the MCPE subreddit. Please do not duplicate your own reports (
MCPE-19439).Thank you for your report!
However, this issue has been closed as a Duplicate of
MCPE-19439.For suggestions, please visit the Minecraft Feedback Site or choose a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
With all due respect, this is NOT an enhancement request or "suggestion". Previous versions of Minecraft PE were functional on iPad mini 1 (and other 512MB iPads). The recent and current versions are simply not usable on this hardware because of the immediate jetsams. Customers who purchased this app when it worked, now find that it does not work. It is very important that you prioritise fixing this. For those customers with 512MB iPads, this issue is more important than any new features, because it prevents them from enjoying the game at all.
It's also inaccurate to consider it a duplicate of
MCPE-19439. Besides the obvious process flaw of marking a report of a bug that's still happening as a duplicate of a bug report that was determined to be resolved, there has also been change between the circumstances ofMCPE-19439. The previous report was against 1.0.0; this bug report is filed against 1.2.3. Between these versions, there were numerous versions of MCPE which were usable.