Besides an issue with page reloading tabs (of which it is in no way certain that it is attributable to a lack of RAM)
I've seen this posted a few times now in several threads. What doesn't tend to come with it is the alternate theory about what else can be the cause of tab reloading other than lack of more RAM. We have Safari tabs on our Macs too. Our Macs tend to have much more RAM than our iOS devices. We don't experience the page reloading problem on our Macs. Sure, Safari on Macs could be coded differently than Safari on iDevices as it pertains to this issue, but I'll ask: what ELSE is as reasonable counterpoint (theory) to explain the page reloading issue if it is not insufficient RAM?
If you're on a Mac, go into "utility" folder and open "Activity Monitor". Click the "Memory" Tab. How much memory is "Safari" and "Safari Web Content" taking? Right now, I have only this one Safari window open (no tabs) and this one, relatively simple (not many images) MacRumors web page opened. It shows 117.8MB for "Safari" and 87MB for "Safari Web Content". I'll grant that Safari on iDevices might be a little leaner than 117.8MB, but even if we cut that to- say- 100MB, it plus one tab of this page is conceptually eating up 187MB of RAM (and note there are other Safari entries in the memory allocation list too- for example, "Safari Networking" at 30.7MB on my machine right now).
If that would be reasonably representative of RAM demand on an iDevice, Safari + about 4 tabbed (simple) pages like this one would eat up all available RAM in a 512K iDevice. But what if we loaded a more elaborate page like- say- CNN:
http://www.cnn.com. Now I've got 2 tabs open: "Safari" continues to show about 115MB, "Safari Web Content" has jumped up to 108MB + 76MB. The CNN page has some streaming media and there are some added RAM-hungry items in the Activity Monitor list reflecting that added demand on RAM. There's basically 2 tabs eating a LOT of RAM. If an iDevice user would open- say- 4 tabs like these: 100MB for a more compact Safari + 108MB times 2 + 76MB times 2 + some related RAM needs for certain media on those pages. Ta-dah. 512K probably exceeded, much of the free RAM in a 1GB pool probably allocated. Now run a few other apps on that iDevice that need their own blocks of RAM.
there have been no wide-publicised issues with a lack of RAM for any application on iOS that I'm aware of.
Because they're coded to what the hardware can handle now. Each App maker knows they have RAM up to the net total available within 1GB. Since they want to maximize their revenues, many (most?) will probably target 512K so they can also sell (or advertise) to the crowd still hanging on to older iDevices that lack 1GB. They are not going to code their apps such that they must have more than 1GB (or probably 512K) such that their apps won't work with current iDevices.
The problem is not any ONE app (though Safari may be considered the exception for some) but in
multitasking several apps, each hungry for a chunk of RAM while the total pool is hard-capped. If the average app maker targets- say- 256K max RAM usage on some concept of taking up to 50% of the 512K of RAM in older iDevices, if a user gets 3 of those running when they each need 256K, they'll cap out almost all available RAM in 1GB iDevices.
Safari tabs can be like running multiple RAM-hungry apps within one program. Each tab can have a fair amount of RAM needs to hold all the content of each page in memory. 256K is not a LOT of memory for modern, image-heavy web pages. Thus, get a few tabs open in Safari and the RAM is going to be consumed. It has to be flushed for other things (or other tabs) to run.
More RAM resolves much of that problem. The RAM flushing will not be as urgent as there would be more RAM in which to persist the content of a web page (and/or run other apps that need chunks of RAM).
If iDevices were single-tasking devices (and let's face it, they almost are in many ways), 1GB or maybe even 512K can be plenty. But multitasking begs for the hardware to support the "
multi" part of that. We have more than 1 core, 64 bit, etc but the crucial RAM remains tight.
Some try to spin the idea that more RAM would lead to lazier programming but that's mostly spin. If Apple believed that, they could still cap max RAM for any one App at some arbitrary (tight) level to mitigate the lazy, so that the free RAM would be there for those multitasking needs such as multiple Safari tabs. For example, Apple could set a hard cap on any one App as if the available RAM was still maxed out at 1GB or 512K. Then the surplus RAM of a 2GB iDevice would be available to better serve the
multitasking need.