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.