Why does it always shows GC_CONCURRENT FREED and GC_CONCURRENT ALLOCATE in Android Logcat while running a app?

Question

I would like to know that why does the below message shows up everytime while running any application.

12-11 17:18:37.141: D/dalvikvm(3155): GC_CONCURRENT freed 485K, 9% free 6696K/7303K, paused 9ms+335ms

paused 9ms+335ms due to this pause my audio which i supposed to play is missing, because as per my code it receives audio data every 40ms so here it paused for 9ms+335ms which is 10 times data loss

I know its performing some kind of Garbage Collection but my question is why does it frequently comes in the logcat.

Thanks for any kind of help!!!!!!

Electrotechnology

what kind of task r u performing? – Forlorn

i m performing audio record and play – Electrotechnology

These are system logs to show memory info of application. – Lenzi

don't worry ... it's nothing unusual – Pedicab

@ALL, I have edited my question, please look at that and give me a solution – Electrotechnology

Answer 1

Garbage Collection is used by Java to prevent you from going Out of memory by removing Objects that are no longer referenced by any class and cannot be reached from your code.

If you have too many of these objects, you will get GC calls alot, which may at some times affect your performance. On the other hand, having Objects that are referenced all the time, may prevent GC from being called (memory leak) and your memory may fill up and you get an OutOfMemoryException.

Your goal is not to eliminate GC, but reduce them as much as possible in methods that are delay sensitive and are running on the UI thread (like onDraw(), getView(), ... for e.g.).

Eppes

I have edited my question, please look at that and give me a solution – Electrotechnology

You still need to minimize object definition to minimize GC. You need to show us the code that plays the audio to assist you in finding these objects. – Eppes

Answer 2

That is normal behaviour for Android. The phone just does garbage collection. For more information checkout the great Google I/O video on this: Google I/O 2011: Memory management for Android Apps

Lilianaliliane

I have edited my question, please look at that and give me a solution – Electrotechnology

You really need to check for optimizations to your code. Sounds like your code requires too much GC's. – Lilianaliliane

Answer 3

Folks, check out these doc/links,its related to memory management:

http://static.googleusercontent.com/media/www.google.com/en//events/io/2011/static/presofiles/memory_management_for_android_apps.pdf

http://eclipse.org/mat/

http://therockncoder.blogspot.in/2012/09/fixing-android-memory-leak.html

Abell