Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Guys, use "top" to see how much memory a given process takes. It'll display process-specific data, NOT cumulative, unlike, say, SBSettings.

An example screenshot, where I've annotated the most memory-hungry processes (AppStore, ooTunes etc.)

http://www.flickr.com/photos/33448355@N07/8937550850/sizes/o/in/photostream/

Note that I don't know of a way of ordering by mem usage, unlike by CPU usage (top -u). The list at http://linux.about.com/od/commands/l/blcmdl1_top.htm is pretty much useless on iOS.

Or just connect it to your computer, run Instruments and look at it there...
 
Or just connect it to your computer, run Instruments and look at it there...

Unfortunately, it isn't guaranteed to work - at least it refused to work with me several times. (I've also recommended this way of CPU / memory usage monitoring in my dedicated article.)
 
Unfortunately, it isn't guaranteed to work - at least it refused to work with me several times. (I've also recommended this way of CPU / memory usage monitoring in my dedicated article.)

It refuses to work for me as well from time to time, I just "re-register" the phone in Xcode and start Instruments again...
 
I thought it was normal behavior. iOS doesn't fully multitask. I think.
I don't find this a normal behavior if I have so much RAM left ..

Guys, use "top" to see how much memory a given process takes. It'll display process-specific data, NOT cumulative, unlike, say, SBSettings.
Well, I'm using SBSettings' free RAM in Status bar. I have 300+ MB free and iOS is closing all my other opened apps when using facebook..
The problem in my case is not how much RAM is used by x and y processes but why iOS is closing my running apps when there is a lot of free RAM!?
 
I don't find this a normal behavior if I have so much RAM left ..


Well, I'm using SBSettings' free RAM in Status bar. I have 300+ MB free and iOS is closing all my other opened apps when using facebook..
The problem in my case is not how much RAM is used by x and y processes but why iOS is closing my running apps when there is a lot of free RAM!?

I'll test the FB app and report back.
 
Ok. Thanks!

Finished testing. What you see is perfectly normal: the Facebook app is VERY sloppily engineered. There doesn't seem to be freeing up resources at all - not even when you send it in the background. On my iPad 3, scrolling thru the main timelist (or whatever it's called - I'm not a really active Facebook user) quickly resulted in the memory usage of the app's increasing to 120 Mbytes.

All in all, the Facebook folks should fire up Instruments and fix the leaks... before that, it will ALWAYS kill suspended tasks.
 
Finished testing. What you see is perfectly normal: the Facebook app is VERY sloppily engineered.
...
All in all, the Facebook folks should fire up Instruments and fix the leaks... before that, it will ALWAYS kill suspended tasks.
Thanks for testing.

What I don't find normal is that iOS decide to close other running apps when I have a lot of free RAM. The OS is responsible for the memory management, not the apps.. I don't think AppStore apps can kill other apps, the iOS itself does that. Appstore apps run in a sandbox environment. Also, as a result of this, we have local storage per apps..
 
Thanks for testing.

What I don't find normal is that iOS decide to close other running apps when I have a lot of free RAM. The OS is responsible for the memory management, not the apps.. I don't think AppStore apps can kill other apps, the iOS itself does that. Appstore apps run in a sandbox environment. Also, as a result of this, we have local storage per apps..

Yup, it's iOS that's killing.

I'll run some serious tests to find out whether this is iPhone 5-specific or also applies to other iDevices and what toggles iOS to do this - the prompt increase in the memory usage of an app or what. The Facebook app can, for example, increase its memory usage from 0 to 120Mbytes in, say, 20 seconds (when you quickly scroll over its list of entries) - iOS may extrapolate it may need a ot more memory based on this and quickly frees up 200-300 Mbytes in advance so that it can be safe even when the Facebook (or any other) app needs 400Mbyte after, say, 20 seconds, it will have.

All this may be connected to the rate (quickness) of memory consumption. While Safari, which is also a memory hog particularly on Retina devices, is far slower to increase memory use (unless you open dozens of tabs in 2-3 seconds), Facebook seems to allocate hundreds of Megabytes of RAM in no time. This may be the reason for iOS' killing backgrounded tasks so quickly when running the FB app, unlike with, say, Safari.
 
Thanks for testing.

What I don't find normal is that iOS decide to close other running apps when I have a lot of free RAM. The OS is responsible for the memory management, not the apps.. I don't think AppStore apps can kill other apps, the iOS itself does that. Appstore apps run in a sandbox environment. Also, as a result of this, we have local storage per apps..

It doesn't happen on my jailbroken iPhone 5, and it's not happening on my girlfriends non-jailbroken iPhone 5. I think it has to do with one of your tweaks, simple as that.
 
The Facebook app can, for example, increase its memory usage from 0 to 120Mbytes in, say, 20 seconds (when you quickly scroll over its list of entries) - iOS may extrapolate it may need a ot more memory based on this and quickly frees up 200-300 Mbytes in advance so that it can be safe even when the Facebook (or any other) app needs 400Mbyte after, say, 20 seconds, it will have.
This sounds as a plausible explanation..

@hafr, I don't know.. this happens with facebook frequently while I can use other apps for hours and this aggressive task killing issue isn't occurring.

I don't think I'm using any facebook related tweak (I've used MesasgeBox in past)
 
For some odd reasons on both my gf and my jailbroken iP5 FB is already running in the background from a fresh reboot or respring. At least thats what sbsettings processes says.....#
 
Finished testing. What you see is perfectly normal: the Facebook app is VERY sloppily engineered. There doesn't seem to be freeing up resources at all - not even when you send it in the background. On my iPad 3, scrolling thru the main timelist (or whatever it's called - I'm not a really active Facebook user) quickly resulted in the memory usage of the app's increasing to 120 Mbytes.

All in all, the Facebook folks should fire up Instruments and fix the leaks... before that, it will ALWAYS kill suspended tasks.

Wow, very good testing! Thank you. I have always suspected as much, the iphone 5 handles FB pretty well, but it crashes regularly with the ipad Mini and I suspect it is due to the lower RAM. Your tests have confirmed that for me. That is if I am evening interperating your tests correctly. ha.
 
but it crashes regularly with the ipad Mini and I suspect it is due to the lower RAM. Your tests have confirmed that for me. That is if I am evening interperating your tests correctly. ha.

You are. There don't seem to be capable iOS programmers at FB... The memory handling of the Facebook app is complete trash - it just doesn't free up resources. I might need to lecture them on iOS programming maybe? :D
 
Wow, very good testing! Thank you. I have always suspected as much, the iphone 5 handles FB pretty well, but it crashes regularly with the ipad Mini and I suspect it is due to the lower RAM. Your tests have confirmed that for me. That is if I am evening interperating your tests correctly. ha.

It never crashes on my iPad 2...
 
Loool, fb never crashed on my iphone 4 on ios 6 or 5, but I kill the app after I stop using it from the multitasking tray.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.