title: Memory leak in FragmentManager
body: <p>Update:</p>
  
  <p>I think the leak is coming from <code>getActivity().getSupportLoaderManager().restartLoader(getLoaderId(), null, this);</code>
  where i have my object implement LoaderCallback. Is there a way for me to clear the callback i tired setting it to </p>
  
  <pre><code>getActivity().getSupportLoaderManager().restartLoader(getLoaderId(), null, null);
  </code></pre>
  
  <p>but this crashes </p>
  
  <p>Orig:</p>
  
  <p>I have a list of objects in one of my fragments(A). When I navigate forward I add fragment A to the backstack.  After I have navigated to a new fragment and I dump the heap. I still see my object in the heap. When I get the shortest path in the dump it looks like below. I can see that in FragmentManagerImpl there is a reference to fragment A in mActive fragments which is keeping my lists object alive. </p>
  
  <p><img src="https://i.stack.imgur.com/UBJLd.png" alt="memory leak"></p>
  
  <p>Is my fragment supposed to stay in mActive fragments or is this a leak?</p>
  
  <p>Adding to backstack</p>
  
  <pre><code>FragmentTransaction transaction = mFragmentManager.beginTransaction();
  updateTransactionWith(info.getReplacement(), transaction, "replace");
  transaction.addToBackStack(info.getReplacement().getClass().toString());
  transaction.commit();
  mFragmentManager.executePendingTransactions();
  </code></pre>