When a Fragment is replaced and put in the back stack (or removed) does it stay in memory?

by

Take a look at this: BackStackRecord.Op.fragment

That is how fragments are stored in the back stack. Note the live reference, neither WeakReference nor SoftReference are used there.

Now this: FragmentManagerImpl.mBackStack

That is where manager stores the back stack. Simple ArrayList, also, no WRs or SRs.

And finally this: Activity.mFragments

That is the reference to the fragment manager.

GC can only collect objects that have no live references (are not reachable from any thread). That means, until your Activity is destroyed (and so, FragmentManager reference is gone), GC will not be able to collect any of the Fragments in the back stack.

Note that when Activity is destroyed and retains state (like when you turn the device to landscape mode), it doesn’t retain actual Fragment objects in the stack, only their states – Fragment.FragmentState objects, i.e. actual fragments in the back stack are re-created every time activity gets re-created with retained state.

Hope this helps.

PS So, in short: Yes, you can run out of memory by adding Fragments to back stack as well as by adding too many views to view hierarchy.

UPD Considering your example, F will stay in memory until C is killed. If C is killed and then resurrected with different configuration – F will be destroyed and reincarnated in a different object as well. So, F‘s memory footprint is around until C loses state or back stack is cleared.

More Related Contents:

  1. My list view is lagging can anyone help me to fix this?
  2. onActivityResult is not being called in Fragment
  3. Replace Fragment inside a ViewPager
  4. Communicating between a fragment and an activity – best practices
  5. OnActivityResult method is deprecated, what is the alternative?
  6. getActivity() returns null in Fragment function
  7. Get root view from current activity
  8. Dilemma: when to use Fragments vs Activities:
  9. Why fragments, and when to use fragments instead of activities?
  10. Error while Running Android Application – Could not initialize OpenglES emulation, use ‘-gpu off’ to disable it
  11. Sharing data between fragments using new architecture component ViewModel
  12. Android Fragment lifecycle over orientation changes
  13. Android : Static Fields and Memory Leaks
  14. Start an activity from a fragment
  15. Further understanding setRetainInstance(true)
  16. How to wrap the height of a ViewPager to the height of its current Fragment?
  17. One Activity and all other Fragments [closed]
  18. What are the differences between activity and fragment?
  19. converting activity into fragment
  20. How to listen for preference changes within a PreferenceFragment?
  21. Difference between extending LifecycleActivity,Activity,ActionbarActivity & AppCompactActivity?
  22. Cannot call getSupportFragmentManager() from activity
  23. How do you create Preference Activity and Preference Fragment on Android?
  24. android:configChanges=”orientation” does not work with fragments
  25. Coordinator Layout with Toolbar in Fragments or Activity
  26. Data Sharing between Fragments and Activity in Android
  27. OnCreateView called multiple times / Working with ActionBar and Fragments
  28. Android: startActivityForResult & setResult for a view class and an activity class
  29. Retain Fragment state between Activities
  30. Android Fragment onCreateView vs. onActivityCreated

Leave a Comment