I've observed this behavior with my own application as well as with the FragmentStack.java found in the example library, found here: http://developer.android.com/resources/samples/Support4Demos/src/com/example/android/supportv4/app/FragmentStackSupport.html
It seems that when you create a number of fragments (say, 4 new ones for this example) and then click "back" repeatedly to go back to the first fragment, then until you create a new Fragment, the previous two will remain in memory. For example: Fragment 1 -> Fragment 2 -> Fragment 3 -> Fragment 4 -> Fragment 5 Go back 4 times now looking at Fragment 1 Fragment 1, 4 and 5 are still in memory. Create a new fragment 6 Fragment 1 and Fragment 6 are in memory now. Is this behavior correct? Is there a reason for it that's not obvious? I'm just not clear on why the fragments I've navigated away from would still be in memory--and only the two last created, and none of the intervening ones. Thanks, Catherine -- 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
