Unless you are a member of the Apple Safari development team, I guess a few hundred more times will do.
Safari is not supposed to crash when it runs out of memory. It is supposed to reload tabs it kicks out. The app you are using at the moment takes precedence, and the others in the background get killed, yes. But not the one you are using at the time (i.e. app crash). So if I am running a game, and I switch to something else, the game will remain there for a while unless the memory is needed. If it isn't, I switch back the game at the spot I was in. If the memory is needed, the game is killed in the BACKGROUND and when I switch back to it, it reloads. NOT CRASH.
Crashing (unexpected quit of the app you are using) is not normal or expected behavior. It is the result of a bug in SOFTWARE. Whether you have 1GB or 5GB, you should always expect the software to behave this way once that FINITE resource called RAM is exhausted.
People here like to hear (read) themselves type claiming this is due to the 1GB of RAM because they read a review somewhere about 64 bit or because this Android tablet or that other tablet has 2GB. Whatever. I expect my apps NOT to crash even with 512MB of RAM, as was the case with previous gen iPads.
So repeating the "1GB is not enough" complaint doesn't make it true. Repeat it as often as you want. It doesn't change the fact that your iPad needs to work with 1GB, because that's all it has. Unless you plan on cracking it open and soldering another GB of RAM in there, or holding out another year for MAYBE another GB of RAM, you better hope Apple fixes it in SOFTWARE.
I really don't think you even trying to listen. Low memory crash isn't so new. All your assumption is build upon that killing all application in backgroud will make enough RAM for Safari.
Let me ask you one thing: when iOS freed all memory it possible can but Safari still takes all these memory, what happens next? iOS itself takes 80% of 512MB on my iPad mini, what happen when there is no memory could possibley freed?
Here is the quote from Apple's document:
Low memory reports differ from other crash reports in that there are no stack traces in this type of reports. When a
low memory crash happens, you must investigate your memory usage patterns and your responses to low memory warnings. This document points to you several memory management references that you might find useful.
When a low-memory condition is detected, the virtual memory system in iOS relies on the cooperation of applications to release memory. Low-memory notifications are sent to all running applications and processes as a request to free up memory, hoping to reduce the amount of memory in use. If memory pressure still exists, the system may terminate background processes to ease memory pressure. If enough memory can be freed up, your application will continue to run and no crash report will be generated. If not, your application will be terminated by iOS because there isn't enough memory to satisfy the application's demands, and a low memory report will be generated and stored on the device.
Yes, iOS will kill all backgroud app and process to free up memory HOPING enough memory could freed for forground application. When there is truely no enough RAM avilable after freeing all possible RAM, iOS will terminate the forground app.
Yes, any app will crash when there is no RAM left and only way to do so is incrase amount of RAM in future product. Putting 1GB of memory is bad move.
