[Asus Transformer TF700] zenaxe:
This is the correct answer.

It is in fact the correct answer to a great many problems/questions on the ICS TFs. This is the problem with nearly every Google app. This is the reason games "designed for Tegra 3" crash consistently on the flagship Tegra 3 tablet. This has probably generated a significant number of RMAs. etc, etc. If this bug had never existed, probably a fourth to a third of the problem threads on the XDA TF Forums and other related boards would not exist.

Some people will claim they don't "have" it or that they have "fixed" it by some hokey method, but this is untrue because it's a driver and memory issue that exists at the kernel level and exists on every TF running the ASUS stock kernel.

The reason people think they can fix it (or think they may not have the problem) is because:

They can work around it

When and how it manifests is highly random and configuration dependent.

I.e. When and how often it manifests depends heavily on the memory state of the system at any given point in time, which in turn depends on a lot of stuff.

So, for example, if you have a bunch of apps/services installed (and virtually everyone's setup is different in this regard, even your own setup will vary over time) it makes a huge difference in how often and when you are going to see it. It's kind of like playing Russian Roulette except it is a giant revolver with 10000 chambers and there can be anywhere from 1 to 10000 bullets chambered every time you pull the trigger (run an app, install a new app, start a new service, etc).

So there are no fixes at the user level (aside from unlocking and installing a custom kernel): ASUS is the only one who can truly fix it for a stock TF.

So, for us, there are only workarounds. After owning five TF devices all of which have regularly been affected by this bug, here is how I deal with it:

On first crash: Run FMR Memory Cleaner, rerun crashed app, this will often "fix" it for a long period if I have not got a lot of stuff installed.

If app crashes after FMR, rerun FMR again. This sounds crazy but if you rerun FMR two times in succession it will usually allocate so much RAM it will force the launcher to reload. NOTE: IT WILL LOOK LIKE THE LAUNCHER HAS CRASHED, IT HASN'T. Wait like 30seconds to a minute for it to restart. Now rerun your app. This seems to give me a new lease on life for 90%+ of the crashes.

However, if your app crashes AGAIN. You guessed it: Cold Boot. Silently curse ASUS and NVIDIA as the machine reboots if it makes you feel better.

NVIDIA discovered acknowledged and FIXED the bug earlier this year. ASUS has either through ignorance, laziness, or malice not incorporated that fix into any of their code prior to the JB kernel for the Nexus 7 and the TF300 (which they probably picked up by osmosis for the 3.x kernel source). IMHO, given the prevalence and impact of this issue, this is evidence that whoever is directing/driving their FW development and/or applications engineering is criminally incompetent.

We will continue to have these issues until ASUS either: fix ICS (won't happen) or release JB. I consider my device usable because I am aware of the issue and can almost always get it to do what I want without a full reboot. However, I pity the poor confused folks whose config causes them to see this often but do not have any technical understanding of the issue or the workarounds.