title: Garbage collector too slow on app with LargeHeap
body: <p>When I started working on my project, I had no idea how to program and was just learning as I went along. My program requires a lot of bitmap graphics and I ran into memory issues early on. I enabled LargeHeap in my app manifest to allow me to use more memory for the graphics, but since then I've learned more about how android handles memory with garbage collector. I made small demo apps to test that GC could keep up with the rate I changed bitmaps and everything worked fine. </p>
  
  <p>But when I try to utilize GC inside my big project, which now has a ridiculous heap of 170mb (the program isn't for general use, so the heap isn't really a concern...I'm just being picky), the memory consumption builds and builds. I've noticed some strange behavior from android in my app in the past that I eventually put down to "the program is probably just too big for the system", so I was wondering if it makes sense to believe that my program is too big or intensive for Garbage Collector to do its thing fast enough? I mean, 170mb heap for an app is  ridiculous enough, right?</p>
  
  <p>EDIT - I'm thinking that a possible solution to the problem, and an answer to my question would come from rewriting the whole program to take advantage of GC. But, as I said, that would involve rewriting the WHOLE thing!! - So I'd rather not bother :D</p>