The best strategy here is to figure out why you're running out of memory
and re-architect your code so you don't even come close. This is a cell
phone and tablet OS, not a surface to air missile OS. There's no need to
be writing code that pushes the hardware to its absolute limits.
On 9/12/2011 6:42 AM, Nick Risaro wrote:
On Sun, Sep 11, 2011 at 4:11 AM, gjs <[email protected]
<mailto:[email protected]>> wrote:
These are typically OutOfMemory errors (not exceptions) which you can
catch in a try catch block, you can then hide these errors from the
user or display a friendly message.
In general you can't do that. If you have an OutOfMemoryError the JVM
can't allocate more memory and then you can't show a message or
something because there is no memory to build the objects.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
