外部配置太大,此过程中的Andr​​oid [英] External allocation too large for this process in Android

查看:141
本文介绍了外部配置太大,此过程中的Andr​​oid的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我收到的外部分配太大,此过程的我的应用程序错误。很多这些一次:

I'm getting "external allocation too large for this process" errors in my app. Lots of these at once:

11-16 10:56:59.230: ERROR/dalvikvm-heap(2875): 1303680-byte external allocation too large for this process.
11-16 10:56:59.230: ERROR/GraphicsJNI(2875): VM won't let us allocate 1303680 bytes
11-16 10:56:59.230: ERROR/dalvikvm-heap(2875): 1536000-byte external allocation too large for this process.
11-16 10:56:59.230: ERROR/GraphicsJNI(2875): VM won't let us allocate 1536000 bytes

看来,他们的生产,同时布局被渲染,装载大位图后。的误差,然而,这并不而位图正在德$ C $光盘生产

It appears that they are produced while the layout is being rendered, after loading large bitmaps. The errors, however, are not produced while the bitmap is being decoded.

我如何调试这些错误?任何额外的指针?

How can I debug these errors? Any additional pointers?

推荐答案

adamp的评论是在我的特定情况下的答案是:

adamp's comment was the answer in my particular case:

该框架往往会捕捉美景   屏幕到临时位图   绘图性能。看起来像   你的应用是推动正对着   它的内存限制已经和这   颠簸过来。看看的   其他建议限制你的   应用程序的内存使用情况。

The framework will often capture views onscreen into temporary bitmaps for drawing performance. It looks like your app is pushing right up against its memory limit already and this bumps it over. Take a look at the other suggestions for limiting your app's memory usage.

这篇关于外部配置太大,此过程中的Andr​​oid的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆