Plus, the tools causes Page Outs. In theory, if Mail is still in memory, a push should Page In in the memory needed when an email arrives.

I tested this on my phone. I reactivated my MobileMe mail, checked that it worked before freeing memory. Then, went into iStat, touched the FREE MEMORY button, and sent myself another email. Sure enough, I got the new email notification sound a second later followed by GPush telling me a new message arrived in Gmail. Heck, even the Gmail account got the message at the same time.

I did the free memory test a second time and got the MobileMe and GPush notifications a second later. The Gmail notification came minutes later this time since it’s set to 15 minutes. It arrived when I went into Mail to delete the MobileMe message.

Mind you, I’m only one of millions, so my results may not be what a majority are seeing. Still, I didn’t see any issues with Push not working when freeing memory.

All that said, maybe Apple should do more with it’s iPhone OS to better handle memory. It’s not good when applications suddenly die with no warning including Apple’s own applications. Mind you, Apples apps very rarely die unexpectedly. Mobile Safari is the only Apple app I have had die suddenly, possibly due to memory. With Safari, it could be many other factors other than memory.

It’s also very unprofessional to tell it’s users to “turn their iPhone/iPod touch off, then back on” to fix this memory issue.

The process for getting apps on the App Store is broken, no doubt. Generally speaking (and there are always exceptions), if Apple has a problem with an app, it needs to be raised before the app is accepted into the store. Removing an app after the fact and especially after people have purchased it is not fair to anyone. Apple taks 30% of the sales but the developer is responsible for refunding 100% of the price. This is a recipe for bankruptcy if I ever saw one.