title: Distinguishing between a memory leak and normal memory usage
body: <p>I am creating an Android app, and I've only just recently begun to examine the memory usage. </p>
  
  <p>My app consists of a main activity and two fragments within (Fragment A holds a recyclerview with images, Fragment B holds an image and some text boxes).</p>
  
  <p>I've noticed that when I start the app, my memory allocation is at roughly 20MB. By scrolling up and down on the recyclerview in Fragment A (not loading any new data) I can make the memory usage increase nonstop (until garbage collection). </p>
  
  <p>Also, if I go from fragment A to fragment B back and forth, I can make the memory allocation increase nonstop (until garbage collection). 20 -> 23 -> 29, .. etc. Until it gets to 60+ and gets garbage collected.</p>
  
  <p>If I start the app at roughly 23MB allocated, and do some scrolling and moving back and forth between fragments, my  memory usage might be somewhere between 40 and 60+ MB. </p>
  
  <p>When I use Android Studio to garbage collect multiple times in a row, I can bring it back down but not all the way to 23 (usually to 30ish). </p>
  
  <p>Is this a memory leak since I'm unable to garbage collect 100% of the memory I started out with? </p>