GC_concurrent 문제를 해결하는 방법은 무엇입니까?

07-06 10:33:28.405: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4688K, 23% free 18428K/23751K, paused 7ms+19ms 
07-06 10:33:29.484: DEBUG/dalvikvm(509): GC_CONCURRENT freed 24K, 14% free 20452K/23751K, paused 7ms+21ms 
07-06 10:33:30.486: DEBUG/dalvikvm(509): GC_FOR_ALLOC freed 4623K, 26% free 17648K/23751K, paused 260ms 
07-06 10:33:31.295: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4K, 18% free 19692K/23751K, paused 6ms+19ms 
07-06 10:33:32.335: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 9% free 21739K/23751K, paused 7ms+24ms 
07-06 10:33:33.334: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 20% free 19206K/23943K, paused 6ms+18ms 
07-06 10:33:34.345: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 12% free 21254K/23943K, paused 7ms+26ms 
07-06 10:33:35.245: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 22% free 18687K/23943K, paused 6ms+17ms 
07-06 10:33:36.275: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 14% free 20735K/23943K, paused 7ms+22ms 
07-06 10:33:37.234: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 25% free 18169K/23943K, paused 7ms+15ms 
07-06 10:33:38.374: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 16% free 20217K/23943K, paused 6ms+28ms 
07-06 10:33:39.547: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 8% free 22258K/23943K, paused 8ms+30ms 
07-06 10:33:40.545: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 20% free 19718K/24455K, paused 6ms+19ms 
07-06 10:33:41.595: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 11% free 21766K/24455K, paused 7ms+24ms 
07-06 10:33:42.575: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 22% free 19199K/24455K, paused 7ms+19ms 
07-06 10:33:43.814: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 14% free 21247K/24455K, paused 7ms+36ms 
07-06 10:33:44.725: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 24% free 18681K/24455K, paused 7ms+17ms 
07-06 10:33:45.724: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 16% free 20729K/24455K, paused 7ms+23ms 
07-06 10:33:46.654: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 26% free 18162K/24455K, paused 7ms+12ms 
07-06 10:33:47.746: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 18% free 20210K/24455K, paused 23ms+21ms 
07-06 10:33:48.917: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 9% free 22258K/24455K, paused 6ms+29ms 
07-06 10:33:49.924: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 20% free 19691K/24455K, paused 7ms+20ms 
07-06 10:33:51.164: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 12% free 21739K/24455K, paused 13ms+24ms 
07-06 10:33:52.174: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 22% free 19172K/24455K, paused 6ms+18ms 
07-06 10:33:53.255: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 14% free 21220K/24455K, paused 6ms+26ms 
07-06 10:33:54.234: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 24% free 18654K/24455K, paused 7ms+17ms 
07-06 10:33:55.324: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 16% free 20701K/24455K, paused 6ms+22ms 
07-06 10:33:56.184: DEBUG/dalvikvm(509): GC_FOR_ALLOC freed 4610K, 28% free 17648K/24455K, paused 242ms 
07-06 10:33:57.025: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4K, 20% free 19692K/24455K, paused 7ms+20ms 
07-06 10:33:58.085: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 12% free 21739K/24455K, paused 6ms+27ms 
07-06 10:33:59.034: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 22% free 19173K/24455K, paused 7ms+19ms 
07-06 10:34:00.204: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 14% free 21221K/24455K, paused 7ms+44ms 
07-06 10:34:01.164: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4614K, 24% free 18654K/24455K, paused 7ms+17ms 
07-06 10:34:02.176: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 16% free 20702K/24455K, paused 7ms+22ms 
07-06 10:34:02.985: DEBUG/dalvikvm(509): GC_FOR_ALLOC freed 4610K, 28% free 17648K/24455K, paused 244ms 
07-06 10:34:03.774: DEBUG/dalvikvm(509): GC_CONCURRENT freed 4K, 20% free 19692K/24455K, paused 7ms+20ms 
07-06 10:34:04.813: DEBUG/dalvikvm(509): GC_CONCURRENT freed <1K, 12% free 21739K/24455K, paused 6ms+28ms

출처

2011-07-06 vimal kumar

+11

와우 .. 가비지 수집을 어떻게 중지할까요? –

이것은지도를 숨기면지도를 사용하기 때문에 괜찮습니다.하지만지도가 필요합니다. –

하지만 어쨌든 앱에 영향을 미치지 않을 것이라고 생각합니다. –

힙은

GC_CONCURRENT freed <1K, 14% free 21220K/24455K, paused 6ms+26ms

GC_CONCURRENT 가득 : 힙 메모리의이 컬렉션 14 %가 무료입니다 후
14% free 21220K/24455K 가득 차서에서 이동합니다. 힙 사용을 점검하십시오.
paused 6ms+26ms 쓰레기 수거에 걸리는 시간.

분명히 수정해야 할 코드에는 엄청난 메모리 누수가 있습니다.

출처

2011-07-06 05:55:39 Reno

코딩은 android 3.0 honeycomb 용이며 코드를지도에 숨기면 아무 문제가 없습니다. –

이 맵 문제는 3.1에서 수정 된 것으로 들었습니다. 그러한 유용한 정보는 – Reno

+1입니다. 나는 또한 비슷한 문제에 직면하고있다. 나는 GingerBird에 두 개의 linkedlists를 사용하고 있습니다. 여기에 내 질문을 참조하십시오 http://stackoverflow.com/questions/10070189/android-audiotrack-message-obtainbuffer-track-0x1d1318-disabled-restarting – aProgrammer

GC_concurrent 문제를 해결하는 방법은 무엇입니까?

답변

관련 문제