On Wed, Dec 26, 2012 at 6:38 AM, Mark Murphy <mmur...@commonsware.com>wrote:
> On Tue, Dec 25, 2012 at 8:35 PM, TreKing <treking...@gmail.com> wrote: > > I believe it is entirely possible and actually a frequent occurrence that > > Activities are destroyed while processes are not. For example, you might > > open a second Activity within your own app that causes memory pressure - > > your process must keep running to show the second Activity but the first > > Activity, which is now hidden, can be destroyed to reclaim memory. > > According to Ms. Hackborn, this does not happen: > > > http://stackoverflow.com/questions/7536988/android-app-out-of-memory-issues-tried-everything-and-still-at-a-loss/7576275#7576275 > > If you can provide a sample app and steps for reproducing the > activities-get-destroyed-for-memory behavior, I'd love to see it! Interesting. Thanks for the link. I was going off the docs you mention in the post. Though I swear I saw this behavior on my G1 ... I'll play around with it when I get back from vaca and post back. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
