This happens with small images as well, it has to do with the Bitmap cache, it's a recurring issue, and it's still in 2.0.
On Nov 24, 9:52 am, Mark Murphy <[email protected]> wrote: > JasonMP wrote: > > Ok, I'm getting a couple things that look funny. > > <snip> > > > 11-24 10:28:52.758: ERROR/AndroidRuntime(4015): Caused by: > > java.lang.NullPointerException > > > 11-24 10:28:52.758: ERROR/AndroidRuntime(4015): at > > com.mallet.tool.Sheet.showStats(Sheet.java:280) > > The "Caused by" portion of the trace is what you want most of the time. > Here, it's saying you have a NullPointerException on line 280 of > Sheet.java. Since the exception is occurring directly on this line (not > in something deeper in Android), you know there is an object that you > are calling a method upon right on that line, and that object is null. > > From your other email: > > > 11-24 10:44:56.768: ERROR/AndroidRuntime(4042): > >java.lang.OutOfMemoryError:bitmapsizeexceedsVMbudget > > This means pretty much what it says: you're trying to load too big of an > image. Bear in mind that Android's garbage collector does not do too > much in the way of compaction, so it is easy to fragment your heap to > the point that, while you may have a lot of memory free, nothing is big > enough to hold a largebitmap. If you are going to deal with large > images, you will need to take extra steps to manage your memory (e.g., > allocate a buffer early and reuse it rather than the more traditional > allocate-and-garbage-collect model). > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 1.0 Available! -- 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
