title: Is GC_FOR_ALLOC more "serious" when investigating memory usage?
body: <p>I'm currently investigating garbage collection problems with my Android app, and I'm curious to know if GC_FOR_ALLOC is indicative of a bigger problem than other GC messages, such as GC_CONCURRENT.</p>
  
  <p>From my understanding, GC_CONCURRENT is doing what the garbage collector should do. The heap has reached a particular limit, better go clean up memory.</p>
  
  <p>GC_FOR_ALLOC suggests to me something more serious is happening if I'm trying to create an object and there's no memory left to do it.</p>
  
  <p>Is there a priority or "seriousness" level for the GC messages?</p>