Hi, 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. Most commonly on this list, they are usually associated with trying to allocate memory for bitmaps that are too large. If so try using smaller of less images & remember to recycle bitmaps when done.
Regards On Sep 11, 7:42 am, Christopher Van Kirk <[email protected]> wrote: > Quite right. Sorry, thought this was on a different list. > > I still think he (or she) needs to review memory usage. Running into the > memory limit is a good indicator of a bad design. > > On 9/11/2011 3:56 AM, TreKing wrote: > > > > > > > > > On Sat, Sep 10, 2011 at 2:36 AM, Christopher Van Kirk > > <[email protected] <mailto:[email protected]>> > > wrote: > > > Check that the pointer returned to you when you allocate memory > > is non-null. If it's null, you're out of memory. > > > You don't use pointers or "allocate memory" directly in Java and even > > if you did you would not be getting back a null pointer - you'll get > > an OutOfMemoryException as the OP is getting. > > > --------------------------------------------------------------------------- > > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices > > > -- > > 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
