Hello again, We've been chasing a wide variety of memory leaks or things that look like potential memory leaks in our program that uses MapViews heavily. The diagnosis so far is sadly not great. I'm hoping someone can help. I've filed a bug on this, but I am looking for advice from people or comments about whether or not they see the same behavior.
I am guessing that there is stuff in the Maps application that works around at least some of these issues. I am attaching 3 screenshots of the Eclipse Memory Analyzer: 1) Shows the MapActivity (subclassed by HistoryDetailsActivity for us) not releasing their connection to system classes, and thus being held in memory. http://android.googlecode.com/issues/attachment?aid=-6844645649729699418&name=MapActivity_leaks.PNG Are there any Android Maps calls that you know that can help avoid this? 2) Shows maps using 23% of process memory (600K at this point) after zooming and panning the map for 20 seconds. This is normally okay, since this is a cache, but the cache looks like it's not using SoftReferences, which seems to make it inflexible/unusuable for apps that actually do want to use the memory. (http://android.googlecode.com/issues/attachment? aid=-1304590382087797856&name=Maphog23percent_afterzoomdragresize.PNG http://android.googlecode.com/issues/attachment?aid=-5424879574327685477&name=MapTiles_lnoweakrefs.PNG) In conclusion, I just wanted to make a wish: let's make more of the maps stuff open source, so people like me can fix these issues. Except for a tiny part of the code, there is no good reason to keep anything closed. P.S. I've added all of this info to: http://code.google.com/p/android/issues/detail?id=2181 -- 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
