Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPad RAM Management is horrible in iPadOS 13.2
- Thread starter Radon87000
- Start date
- Sort by reaction score
Me too. Surprisingly 13.1.2 & 13.1.3 are both still signed (still possible to downgrade).https://ipsw.me is the place I’ve used for years.
About / IPSW Downloads
Download current and previous versions of Apple's iOS, iPadOS, watchOS, tvOS, audioOS and macOS firmware and receive notifications when new firmwares are released.ipsw.me
You can never have "enough" RAM on device that can suspend an infinite amount of apps for an infinite amount of time. Eventually an app will refresh. 6gb MIGHT be good for the OP work load but not for the guy that is doing that PLUS editing a video in Adobe (iPad).
Apple intentionally uses the minimum amount of RAM required to keep apps optimized. If you increase the amount of RAM available little will change because App Devs will just optimize their apps less. Its no different than if you have a 8gb storage device and 512gb. The 8gb you are constantly micromanaging and streamlining what is on it, the 512gb device you are downloading movies without even a plan to watch them.
Devices with more RAM need more RAM. The allowance an app can use in the foreground is based on the devices requirements. For example an iPhone X can use 1.2gb of 3gb memory with a foreground app. And iPad Pro can use 3gb of 4gb memory with a foreground app. More data at higher resolutions requires more memory. Even though that leaves 1.8gb for the background with the X and 1gb for the background with the iPad Pro that doesn't mean it will have better performance because it could have more hardware running in the background for cellular hardware based apps and things of that nature.
Certain other mobile operating systems control memory usage via built in mechanisms. This is due to lack of accessibly and control the apps have over the memory, especially if the are running in a java virtual machine for example (which also requires more memory and is not an efficient use of memory a lot of the time).
With iOS the apps have control of memory usage with the OS forcing its hand when there is a problem.
Your foreground apps can only use a specific amount of of RAM before they get a warning (at that point they need to discard data) from the OS framework used for memory (might be metrickit?), if they exceed the limit iOS will terminate the app with an OOM error (out of memory).
Your background apps (depending on APIs), as soon as they go into the background are immediately going to snapshot where you are, hide private/sensitive data from the app switcher, release control of hardware (camera, mic, etc), and release memory (data is cached, foreground has priority to purge and use it if needed). And they are supposed to discard large data that can be reloaded. However if you do that when you open the app it could look like its refreshing from scratch but its reloading large assets like images. If you do not do that your app is a larger target for being pushed out of memory by a foreground app (priority).
So a single app that is poorly optimized for foreground use can cause your background apps to need to reload. Or if its poorly optimized for background use it can cause itself to be purged due to being to large or terminated by the OS for not doing what its supposed to do.
On top of that every update that adds any feature with a system background function potentially uses the RAM that was previous allotted for background task and suspended apps cached data. This isn't limited to features either, spotlight needs to index, iOS is updating other devices (WatchOS, HomePods, AirPods) and can settle back to the way it was once its all done.
Web browsers tabs will always refresh if its a ad laden webpage. A webpage with adds that cycle or even worse play a video could grow indefinitely. I picked one I knew while I was tying this and let it run int he background of MacOS, started at 100mb and now its 1.26gb.
That single webpage (granted desktop version in this case) would cause all sort of things to refresh. Its exceeding the total allowance of memory usage for most iPhones all by itself.
TL;DR Its normal behavior if you are going to mimics swap use although it does seems the OP and people here are noticing a "change" with apps refreshing (I haven't YET) so it could be a bug, a temporary function running in the background like spotlight or photos manipulation (metadata updating) or storage optimization services (iCloud messages and photo library), or new "features" just using more memory.
However generally its an app. Not always but most of the time. Memory leaks are generally the reason an will go from full speed to immediately crashing to the home screen.
Apple intentionally uses the minimum amount of RAM required to keep apps optimized. If you increase the amount of RAM available little will change because App Devs will just optimize their apps less. Its no different than if you have a 8gb storage device and 512gb. The 8gb you are constantly micromanaging and streamlining what is on it, the 512gb device you are downloading movies without even a plan to watch them.
Devices with more RAM need more RAM. The allowance an app can use in the foreground is based on the devices requirements. For example an iPhone X can use 1.2gb of 3gb memory with a foreground app. And iPad Pro can use 3gb of 4gb memory with a foreground app. More data at higher resolutions requires more memory. Even though that leaves 1.8gb for the background with the X and 1gb for the background with the iPad Pro that doesn't mean it will have better performance because it could have more hardware running in the background for cellular hardware based apps and things of that nature.
Certain other mobile operating systems control memory usage via built in mechanisms. This is due to lack of accessibly and control the apps have over the memory, especially if the are running in a java virtual machine for example (which also requires more memory and is not an efficient use of memory a lot of the time).
With iOS the apps have control of memory usage with the OS forcing its hand when there is a problem.
Your foreground apps can only use a specific amount of of RAM before they get a warning (at that point they need to discard data) from the OS framework used for memory (might be metrickit?), if they exceed the limit iOS will terminate the app with an OOM error (out of memory).
Your background apps (depending on APIs), as soon as they go into the background are immediately going to snapshot where you are, hide private/sensitive data from the app switcher, release control of hardware (camera, mic, etc), and release memory (data is cached, foreground has priority to purge and use it if needed). And they are supposed to discard large data that can be reloaded. However if you do that when you open the app it could look like its refreshing from scratch but its reloading large assets like images. If you do not do that your app is a larger target for being pushed out of memory by a foreground app (priority).
So a single app that is poorly optimized for foreground use can cause your background apps to need to reload. Or if its poorly optimized for background use it can cause itself to be purged due to being to large or terminated by the OS for not doing what its supposed to do.
On top of that every update that adds any feature with a system background function potentially uses the RAM that was previous allotted for background task and suspended apps cached data. This isn't limited to features either, spotlight needs to index, iOS is updating other devices (WatchOS, HomePods, AirPods) and can settle back to the way it was once its all done.
Web browsers tabs will always refresh if its a ad laden webpage. A webpage with adds that cycle or even worse play a video could grow indefinitely. I picked one I knew while I was tying this and let it run int he background of MacOS, started at 100mb and now its 1.26gb.
That single webpage (granted desktop version in this case) would cause all sort of things to refresh. Its exceeding the total allowance of memory usage for most iPhones all by itself.
TL;DR Its normal behavior if you are going to mimics swap use although it does seems the OP and people here are noticing a "change" with apps refreshing (I haven't YET) so it could be a bug, a temporary function running in the background like spotlight or photos manipulation (metadata updating) or storage optimization services (iCloud messages and photo library), or new "features" just using more memory.
However generally its an app. Not always but most of the time. Memory leaks are generally the reason an will go from full speed to immediately crashing to the home screen.
Last edited:
Problem is... same apps, same phone, same users. Only different OS that made things getting worst. We called these as bug / defect.
Yup. The worst thing about this issue is that it was reported many times early in 13.2 beta testing, but the bug still made it to release. This is a major issue and should have been fixed immediately.
I experienced that right after 13.2 update. I normally had few apps open, primary for communication and social media apps.... It's constantly reloading if the app is in background. Hopefully this will be fixed soon......
Yeah I literally have 1 tab open (this thread) and I switch to Instagram then to news and when I come back, boom it’s reloading! This happens all the time now. Way different behavior compared to iOS 12 which I was just on a few days ago. Safari had some sort of priority over other apps and would remain in memory much longer. Now it’s the lowest in priority for some reason or is buggy and crashing in the background.
For some reason my other apps are hanging on almost the same or better than before. It’s just safari for me!
For some reason my other apps are hanging on almost the same or better than before. It’s just safari for me!
Last edited:
Same here. I was very supporised how OneDrive behaves on 13.2 - I use it to sync my photos and on 12.x it managed easily to work in a background to sync photos seamlessly while on 13.2 it is killed almost instantly i swith off screen, regardless if ipad or ios is battery or charging. shame on you apple
iOS 13 is killing background apps more frequently, iPhone owners report
Apps are getting killed in the background.
www.theverge.com
I always thought that multitasking on ios just means browsing screenshots on the latest screens
Whatever you do with your device, using control center, launching another app - ”everything else” is paused. I quess that could be called ”pro-tasking” instead of multitasking.
And it is not only 13,2 issue - been there and will be there as long as ios is what it is.
As long as i remember people have always said how optimized and great ios is. It never had been and it isnt now either. It was and it is horrible for multitasking - and it should have be named ”pro-tasking” on ios.
Last edited:
I’m proud to see that the media is helping us, users, to face Apple with this non solved bugs that, apparently, aren’t annoying for them.
I’d like to see the same response towards a feature recently removed, the smart zoom. It would be cool if sites like The Verge, Macrumors or Ars Technica made an article complaining how we can no longer double tap in order to adjust the text to the width of the screen.
Thank you for raising your voice against giants like Apple, to make our voices count.
I’d like to see the same response towards a feature recently removed, the smart zoom. It would be cool if sites like The Verge, Macrumors or Ars Technica made an article complaining how we can no longer double tap in order to adjust the text to the width of the screen.
Thank you for raising your voice against giants like Apple, to make our voices count.
As a temporary fix. This works for about a day for me. Force reboot the device, a standard restart won’t do anything. After doing this I can go most of the day without this happening in Safari or other apps. No one should have to do this but it does work, for a while.
So if I download the signed 13.1.3 from IPSW.me how long do I have to install it .. will it still work after apple stops signing it? Can I update my 2017 12.9 iPad Pro that still has 11.3.1 on it to it?
Thanks
I guess you can update to 13.1.3 as long as Apple is still signing it... Which may last a few days, or maybe just hours, who knows.
So another words just because you downloaded a signed IPSW and have it stored on a hard drive doesn’t mean you can store it for a year on said hard drive then install it a year later? I guess when you try next year to update with the IPSW on your hard drive and you point iTunes to it .. itunes is going to look at that IPSW file and say ‘sorry that ain’t signed no more’ ..... correct?
Correct. In order to able install the downloaded update, you must be online and get ‘ticket’ from Apple at the time you run the installation.
Will add to all these, on both my iPhone XS and my 6th-gen iPad, the RAM management has been FAR too aggressive closing apps:
- iPad: By far the most annoying behaviour is with Evernote - try to take some notes in a meeting now, I dare you. If for some reason you swap away to a browser, or the iPad locks itself - great news! let's reload the entire app from scratch and force you to re-enter editing mode and scroll down to where you were taking notes just 1 minute ago!
- iPhone: You have Sonos? Well enjoy reloading the controller app from scratch every time you put the phone down. And those lock screen controls? Hope you're quick off the mark, or they'll disappear within, oh, 30 seconds.
- iPad: By far the most annoying behaviour is with Evernote - try to take some notes in a meeting now, I dare you. If for some reason you swap away to a browser, or the iPad locks itself - great news! let's reload the entire app from scratch and force you to re-enter editing mode and scroll down to where you were taking notes just 1 minute ago!
- iPhone: You have Sonos? Well enjoy reloading the controller app from scratch every time you put the phone down. And those lock screen controls? Hope you're quick off the mark, or they'll disappear within, oh, 30 seconds.
It's like back to the iPhone OS 3.0 era with no multi-tasking. Does anybody even do any QC anymore at Apple? I was browsing a Wikipedia article in Safari, locked the screen and did some other business. Unlocked the phone and Safari reloaded the whole page just after 5 minutes.
I’m just glad that this issue is gaining national media attention. Macrumors and 9to5 have posted about it. Typically when big articles are written Apple fixes them sooner rather than later. I feel confident that either in the next public release or betas we’ll see this issue corrected. Thank god
Well I think I'll hold off on this update, would be the first time I've skipped an update. I just got another 3 day battery cycle wouldn't want to mess that up either.