because they're suspended and their current state is saved in RAM?
if your PC / Mac is in sleep mode, do you consider it "turned on" aswell just because it skips the booting screen? :/
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.
Multitasking leaves apps open!!
- Thread starter cameljok
- Start date
- Sort by reaction score
because they're suspended and their current state is saved in RAM?
if your PC / Mac is in sleep mode, do you consider it "turned on" aswell just because it skips the booting screen? :/
I'm not sure why I'm bothering to respond, given the mentality I usually associated with the "owned" meme (at least it was "pwned" ...) but it's worth noting that the operating system goes out of its way to hide the details of what's really going on.
If by "open" you mean getting CPU time, eating up battery life, actively performing tasks, etc. then applications that aren't in the foreground usually aren't "open." Most applications are completely suspended when they're in the background - they're resident in memory but that's it (and they're supposed to aggressively reduce their memory usage before being suspended.) There are obvious exceptions for applications playing background audio, navigation, and so forth, but very few applications fall into this category.
So if by "open" you mean the application is still in memory? Maybe. A foreground application that needs a lot of memory will reclaim memory used by suspended applications. So there are indeed instances when an application that has been suspended will launch from scratch and you'll see the splash screen again. Just because it shows up in the "tray" of recently used applications doesn't mean it's tying up memory.
Again, free memory is wasted memory. Until you need it for something else there's no reason not to keep something in it that might speeds up future operations. I hate to break it to you, but every modern operating system executable uses available memory as a disk cache so that re-launching an application you've just exited is faster. Quitting an app in Windows or OS X doesn't "get rid of it", either. iOS just goes the next step and allows the app to pick up from where it left off if the memory isn't needed for anything else.
As for your signature?
He pretty clearly told people not to hold it in a way that causes reception problems. When you're not having reception problems you can hold it any way you please! It's like nobody here ever owned a cell phone before. Or a radio. Or anything else that relies on wireless communication subject to RF interference.
An iOS developer needs to do work to make sure an app that restarts comes back to a place that makes sense, with the default being a clean start . They also need to do work to make sure an app that was previously running and hasn't been unloaded comes back to a place that makes sense, but in this case the default is to be exactly where you left off.
Developers are still working through the implications and we'll see them become more consistent over time. Right now there are definitely some rough spots - Facebook and Foursquare are both more annoying as a result, but they have all the tools they need to do the right thing.
This might actually be useful if you're someone who manually customizes his brightness levels alot; or turns 3G / WiFi on and off alot for battery saving purposes
So dramatic. Actually, the end result is pretty much the same with all current mobile OS's.
Processes pushed to the background use up memory but no CPU time unless they have a reason to. (Such as location monitoring or downloading.) In other words, they're suspended until brought forward again.
When a foreground process needs more memory, the OS asks other processes to give up memory (Safari used to get this request a lot) or chooses a suspended app to kill to reclaim its resources.
The user normally doesn't need to do anything special, unless a process has a bug. Which is why all of them include a way to stop a process if need be.
--
Btw, everyone needs to stop giving others grief for not understanding Apple's paradigm. Judging from all the questions on iPhone forums, it has confused a lot of people.
Users need a model to understand their device behavior and this one is not at all intuitive, since every app shows up in the popup list, but apps actually running in the background have no special indicator on their icon.
cause they are in a paused state. he meant not open as in not running and taking up battery I assume
Because they aren't open - they are in a "saved" state.
But I don't think every app has been coded well and I do think there are "leaks". I posted last week that I tried to open an app and it got stuck. I couldn't get the app to run until the phone was either rebooted or I went to the task manager and killed it manually. When it re-ran then - it worked fine.
Take that for what it's worth
Since we have beat the multitasking to death, why not add a few more comments about spaces--and I will add my vote to it being a great concept and one well implemented in OS-X. I love it--it is like having 4 computer screens. Certainly not counter-intuitive--not to me anyway.
Yeah, my thoughts are you should really do a little research and learn exactly how Apple implemented multitasking on their platform before you create such ridiculous topics.
http://whenwillapple.com/blog/2010/04/19/iphone-os-4-multitasking-explained-again/
If you got the phone and you hadn't read how the feature worked you would be confused.
People are used to Windows or Mac OS X where only running applications would appear in the Dock/Taskbar.
iOS keeps any App that you have opened since startup in the switcher.
not really.
my understanding is that the app stops, like when you leave a playing movie in vlc or quicktime and the inactive window pauses.