android - GC_FOR_ALLOC freed 6346K, 7% free , paused 143ms, total 143ms

27,490

This is not an error, but an information that Garbage collector has run.

If you are seeing a lot of those, it might mean that you are making many allocations or have little memory. You should try to improve your program's memory performance.

There is a good source information about investigating RAM consumption in Android:

https://developer.android.com/tools/debugging/debugging-memory.html

There is also a document about general strategies for managing your memory consumption in Android:

http://developer.android.com/training/articles/memory.html

Share:
27,490

Related videos on Youtube

zIronManBox
Author by

zIronManBox

Updated on July 09, 2022

Comments

  • zIronManBox
    zIronManBox almost 2 years

    I'm developing an offline mapView using OSMdroid Library. My tilesource loads the tiles but renders quit steadily. But the fact is in my log messages, I keep getting this error:

    GC_FOR_ALLOC freed 6346K, 7% free , paused 143ms, total 143ms

    I'm not sure how to debug this? Any ideas, do I have any memory leaks?

  • Maveňツ
    Maveňツ about 10 years
    nice explanation for new commers ;)
  • gruszczy
    gruszczy about 10 years
    The second document was very useful&enlightening to me.
  • zIronManBox
    zIronManBox almost 10 years
    @gruszczy I'd one more msg popping, 05-12 11:51:06.581: I/Choreographer(6837): Skipped 392 frames! The application may be doing too much work on its main thread.
  • gruszczy
    gruszczy almost 10 years
    Well, you are doing some heavy processing in your Activity thread. You need profile your application and probably move some code to a separate thread or to a service.
  • zIronManBox
    zIronManBox almost 10 years
    @gruszczy how do I profile my application? I've heard about DDMS method profiling, but I've not understood correctly. Any tips to understand the same?