GC_CONCURRENT running non-stop
Question
I see the following in my cmd window when using adb logcat
Is this indicative of a memory leak? My assumption is that java garbage collection is running continuously, but I'm not sure. Any clarification is welcome!
1 answers
solution1
1 2014-07-24 19:56:09
Is this indicative of a memory leak?
The best test is to see how much memory is used after a GC. As you can see it starts at 36% and finishes at 36% so if there is a leak it is pretty small.
More likely you are;
- allocating too fast
- not using enough heap
- not GCing as much as you think. ie do you know this is a problem?
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Android GC_CONCURRENT and soundbox app development
how to prevent GC_CONCURRENT statements in Logcat
Android memory leaks heap gc_concurrent
Using Bitmap.createBitmap causes GC_CONCURRENT messages
Calling Calendar class functions produces GC_CONCURRENT messages
Java/Android : Phonegap Contacts API memory leaks, GC_FOR_ALLOC and GC_CONCURRENT
Display Freezes, Force Close or Wait, and GC_MALLOC and GC_Concurrent are Triggered
Tandem/Non-Stop Socket programming
Non-stop Garbage Collection in 2D surfaceview animation
Problem getting Java Streams in HP Tandem (Non-Stop)
Related Tags