My bad. I'll defer to Romain on this. My apologies. Josh Beck
On Dec 9, 8:36 am, Romain Guy <[EMAIL PROTECTED]> wrote: > There is absolutely no such limitation of 640k. > > On Dec 9, 2008 6:21 AM, "joshbeck" <[EMAIL PROTECTED]> wrote: > > I can maybe help here. I'm an amateur, but the 'out of memory' error > is > a familiar adversary. > > The VM only allows you to use 640k at any given time. > I have a program that utilizes hundreds of large bitmap files. Here is > how I > decided to handle it. (It's clunky and inefficient, but it works.) > > -I keep solid track of how much memory is being used at any given > time. > Once the program gets anywhere near 500k, (Just to be safe), > I find a way to call finish, recycle bitmaps, and call an intent to > start a fresh activity. If it's possible to start a fresh activity > when > the memory limit gets close, you may want to consider that > as an option. > > -Also, if you are using images. Load your pics into photoshop or the > Gimp > and make sure they physically as small as you can get them. > > I don't know if any of that will help, but I've learned the hard way > that the 600k ceiling for > memory is something you have to keep a count on. > > Josh Beck > > On Dec 9, 7:07 am, Guillaume Perrot <[EMAIL PROTECTED]> wrote: > When > we have an OutOfMemor... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
