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
<christopher.vank...@gmail.com <mailto:christopher.vank...@gmail.com>>
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
