On Tue, Dec 25, 2012 at 8:35 PM, TreKing <[email protected]> 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! > Also, even simpler, rotate your device. Activities destroyed. Processes, not > so much. Correct. Ditto for any finish() scenarios (e.g., BACK, FLAG_ACTIVITY_CLEAR_TOP). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Aqui estão alguns sites onde você pode perguntar ou responder dúvidas sobre desenvolvimento de aplicações para Android: http://www.andglobe.com -- 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
