android - GC_FOR_ALLOC 释放 6346K, 7% free , paused 143ms, total 143ms-移动开发问题

android - GC_FOR_ALLOC freed 6346K, 7% free , paused 143ms, total 143ms(android - GC_FOR_ALLOC 释放 6346K, 7% free , paused 143ms, total 143ms)

本文介绍了android - GC_FOR_ALLOC 释放 6346K, 7% free , paused 143ms, total 143ms的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我正在使用 OSMdroid 库开发离线 mapView.我的 tilesource 加载了瓷砖，但呈现稳定退出.但事实是在我的日志消息中，我不断收到此错误:

GC_FOR_ALLOC 释放 6346K，7% 空闲，暂停 143ms，总共 143ms

我不确定如何调试它?任何想法，我是否有任何内存泄漏?

解决方案

这不是错误，而是垃圾收集器运行的信息.

如果您看到很多这样的情况，这可能意味着您进行了很多分配或内存不足.您应该尝试提高程序的内存性能.

有一个很好的关于调查 Android 中 RAM 消耗的来源信息:

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

还有一份关于在 Android 中管理内存消耗的一般策略的文档:

http://developer.android.com/training/articles/memory.htmlp>

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?

解决方案

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

这篇关于android - GC_FOR_ALLOC 释放 6346K, 7% free , paused 143ms, total 143ms的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！