Android 如何解决GC_并发释放? 07-06 10:33:28.405:DEBUG/dalvikvm(509):GC_并发释放4688K,23%释放18428K/23751K,暂停7ms+19ms 07-06 10:33:29.484:DEBUG/dalvikvm(509):GC_并发释放24K,14%释放20452K/23751K,暂停7ms+21ms 07-06 10:33:30.486:DEBUG/dalvikvm(509):GC_FOR_ALLOC释放4623K,26%释放17648K/23751K,暂停260ms 07-06 10:33:31.295:DEBUG/dalvikvm(509):GC_并发释放4K,18%释放19692K/23751K,暂停6ms+19ms 07-06 10:33:32.335:DEBUG/dalvikvm(509):GC_并发释放

Android 如何解决GC_并发释放? 07-06 10:33:28.405:DEBUG/dalvikvm(509):GC_并发释放4688K,23%释放18428K/23751K,暂停7ms+19ms 07-06 10:33:29.484:DEBUG/dalvikvm(509):GC_并发释放24K,14%释放20452K/23751K,暂停7ms+21ms 07-06 10:33:30.486:DEBUG/dalvikvm(509):GC_FOR_ALLOC释放4623K,26%释放17648K/23751K,暂停260ms 07-06 10:33:31.295:DEBUG/dalvikvm(509):GC_并发释放4K,18%释放19692K/23751K,暂停6ms+19ms 07-06 10:33:32.335:DEBUG/dalvikvm(509):GC_并发释放,android,garbage-collection,Android,Garbage Collection,堆已满 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/dalvik

堆已满

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

GC\u。。你在问,如何停止垃圾收集?这是因为如果我隐藏地图,使用地图是可以的,但我需要地图,但我相信这不会影响你的应用程序。不幸的是,这个问题被关闭了。很明显,他们在问什么,这是开发人员在使用某些类型的视图时面临的问题。完全同意你的观点,dpk。编码是针对android 3.0蜂巢的,我在代码中使用地图,如果我隐藏地图,就没有这样的问题。我听说这个地图问题在3.1中得到了解决。不确定。+1获取这样有用的信息。我也面临着类似的问题。我正在姜鸟上使用两个链接列表。请看我的问题,内存泄漏通常是由于PNG图像造成的,尤其是透明图像?在制作游戏应用程序时,我碰巧突然关闭,但没有通过Logcat写入错误消息。
GC_CONCURRENT freed <1K, 14% free 21220K/24455K, paused 6ms+26ms