iOS apps can have memory leaks. iOS apps in a suspended state cannot have memory leaks because they use no memory.
Disk space leaks, sure. But not memory leaks.
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.
Why do Apple Geniuses recommend killing apps manually?
- Thread starter iphnhelp
- Start date
- Sort by reaction score
iOS apps can have memory leaks. iOS apps in a suspended state cannot have memory leaks because they use no memory.
Disk space leaks, sure. But not memory leaks.
No, no, no, no no...
"While suspended, an app remains in memory but does not execute any code." - iOS programming Guide
Suspended Apps can't "produce" memory leaks, because they're not running any code. They can have memory leaks that existed before the suspension, though.
Re-read what I said. A suspended app cannot have a memory leak because it cannot use memory. An app which has been suspended CANNOT allocate memory, therefore it cannot have a leak. A previous leak ISNT a leak of a suspended app, it's the leak of a running app which has been suspended. Those two are very different. Not executing code, means no extra ram can be used, and thus no memory leaks are possible.
Anyway, I'm out of this thread. I've reported it suggesting it be closed since it's nothing more than bickering now.
Actually, it just takes the leak with it into memory. Both of you are correct. The app itself can't allocate memory, the OS can and does as the app requests it.
The point is, that you said, suspended apps don't use any memory which either is false or just mistakable, if you mean it doesn't actively use memory, but still "uses" it passively.
If you'd relax you'd see that I'm actually on your side stating, that there is no need to empty the recent apps list.
I'm sorry did you confuse this for the Android forums? Show me one Apple official guide or documentation that backs your claim.
I'm sorry did you confuse this for the Android forums? Show me one Apple official guide or documentation that backs your claim.
They are correct. With background app refresh and location access under privacy, failure to not kill apps manually will have severe battery drain issues. I have a fairly new 5s. The battery can go from 100 to 50% in 2-3 hrs with me touching the phone because I left stuff running. Since then I've changed things ... Idle my phone goes from 100 to 98% in 8hrs
Even that may not help as background app refresh can allow an app to run a daemon when the main app isn't running. This is all common knowledge but I'd be happy to list the apple source documentation.
Facebook is the WORST offender. With background refresh on plus giving it full location access results in FB CONSTANTLY running in background. Since it's constantly active , it'd be one of the last apps iod terminates unless a foreground app needs the resources
So... A few easy things, disable background app refresh. Then you don't have to manually terminate apps. Or enable it and disable it for every app except the one, or few, you want background processing
Last edited:
The problem is more and more apps DONT suspend. Especially if they have permission in background app refresh not to be suspended.
Facebook is te worst. You can terminate the app, and if it is set to background refresh, it has a service/daemon that runs non stop using ram, CPU, bAttery.
With this running, the mOST memory I can free up on my 5S or iPad 5 (air) is 400mb. After it has run all day... 300mb. It's a ram pig and iOS allows it... I turned it OFF in background app refresh. No more fast battery drain, and I can free up 500-550MB ram
Last edited:
They don't suspend, they get suspended and this is the big difference: They don't have a choice. It's not like they can freely choose to work in the background.
With iOS 7 Apps were allowed to download small amounts of content if either a push notification arrives or the system tells the app it can do so. The system decides and it evaluates the power usage after an app has done its download and gets suspended again. If its too large, iOS can decide to not to give the app anymore background time.
Anyway what's your point towards this thread anyway? Deleting an app out of the recents list doesn't prevent it from background refreshing, so there wouldn't be a point to do so. The user can, as you stated correctly, prohibit it in settings.
I have background app refresh turned on for all my apps, I keep bluetooth, gps and wifi on all the time and see 10-12 hours of a battery life.