> > Watch the memory size balloon fantastically too. > > That is an unfortunate but necessary side effect. Note that the system > will pretty aggressively free up that memory whenever the user > switches to another app.
It balloons to such a degree that it should really be noted in the documentation for the attribute. I spent a couple of days trying to find the memory leak bug in my app that turned out to be this. The app has a constant service running and the process was taking up on the order of 70MB directly after leaving the UI instead of the usual 20MB (especially pronounced if the user viewed documentation in a webview while in the UI). Visiting other applications does help, but still left around 26MB over time. In other words, the attribute seems to be no-lose-why-not-turn-it-on, but actually needs a cost-benefit decision. Pent -- 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
