On Apr 28, 6:28 pm, Ward Willats <[email protected]> wrote: > So this separate "pile" for bitmaps doesn't grow with the VM heap -- > in fact, growing the VM heap made it smaller (I think) because, as > you say, that space came out of total 16 MB allocation (?)
Yup. The way you make more space for bitmaps is by using less space for everything else. > I mean, I could always use LESS memory, but dang...it seems like > since I am well under-budget 16MB wise, there should be some way to > make this work... Well, that's the interesting question: how much memory are you *actually* spending on bitmaps? There isn't a good tool for figuring that out at this time. There is, however a somewhat bad one: you can parse the GC events out of the event log. The process is described here: http://groups.google.com/group/android-developers/browse_thread/thread/6c90a2c70f3593f1/7974ba6fe0361e91?q=fadden+event+log#7974ba6fe0361e91 I'm going to try to throw something together in python or C that does the number-crunching on the log. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
