正如标题所说,我在加载布局时抛出了内存不足异常。有人会认为这是一个内存泄漏问题,但在与它斗争了 2 天后,我不再那么确定了。该应用有 10 多个 Activity ,其中大部分都有背景图片。
我的一些事实/发现:
到目前为止,问题只出现在运行 Android 4.0.3 的 Galaxy Nexus 上。我无法在 Nexus S (4.1.1) 和 Galaxy S II (2.3.3) 上重现它。
屏幕方向不会改变。事实上,无论如何我的大部分 Activity 都锁定在纵向。
只是为了开玩笑,我在打开新 Activity 时添加了对
finish()
的调用,因此当时内存中不会有超过一个 Activity 。已验证正在调用onDestroy
。
定义为:
@Override
public void onDestroy()
{
super.onDestroy();
cleanupDrawables(contentView);
// null all the fields referencing views and drawables
System.gc();
}
其中 cleanupDrawables()
是:
protected static void cleanupDrawables(View view)
{
cleanupDrawable(view.getBackground());
if (view instanceof ImageView)
cleanupDrawable(((ImageView)view).getDrawable());
else if (view instanceof TextView)
{
TextView tv = (TextView)view;
Drawable[] compounds = tv.getCompoundDrawables();
for (int i = 0; i < compounds.length; i++)
cleanupDrawable(compounds[i]);
}
else if (view instanceof ViewGroup && !(view instanceof AdapterView))
{
ViewGroup vg = (ViewGroup)view;
for (int i = 0; i < vg.getChildCount(); i++)
cleanupDrawables(vg.getChildAt(i));
vg.removeAllViews();
}
}
protected static void cleanupDrawable(Drawable d)
{
if (d == null)
return;
d.setCallback(null);
if (d instanceof BitmapDrawable)
((BitmapDrawable)d).getBitmap().recycle();
else if (d instanceof LayerDrawable)
{
LayerDrawable layers = (LayerDrawable)d;
for (int i = 0; i < layers.getNumberOfLayers(); i++)
cleanupDrawable(layers.getDrawable(i));
}
}
查看 Eclipse 堆检查器,内存看起来很稳定,即一些 Activity 比其他 Activity 占用更多内存,但它在关闭时释放,并且随着时间的推移看起来很稳定。
根据 SO 图像的相关答案存储在 native 内存中,但是 this伙计声称他们应该从 Android 3 开始就在堆上,所以如果这确实是图像内存泄漏,我应该会看到内存增加。
我努力的最终结果是我仍然遇到内存不足错误,尽管没有以前那么快。在错误发生之前,我开始看到可见的位图损坏,而在我添加 cleanupDrawables()
代码之前情况并非如此。我推断调用 Bitmap.recycle()
会导致损坏,即使此代码仅在 onDestroy
上调用。损坏出现在两个位图上,这些位图是出现在许多 Activity 中的常见样式的一部分,也出现在仅显示在一个 Activity 中的位图上。
简而言之,我的调查结果尚无定论。此时我不知道还能尝试什么。
供引用的错误堆栈跟踪:
08-22 10:49:51.889: E/AndroidRuntime(31697): java.lang.RuntimeException: Unable to start activity ComponentInfo{klick.beatbleeds/klick.beatbleeds.Bleeds}: android.view.InflateException: Binary XML file line #67: Error inflating class <unknown>
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1955)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1980)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread.access$600(ActivityThread.java:122)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1146)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.os.Handler.dispatchMessage(Handler.java:99)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.os.Looper.loop(Looper.java:137)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread.main(ActivityThread.java:4340)
08-22 10:49:51.889: E/AndroidRuntime(31697): at java.lang.reflect.Method.invokeNative(Native Method)
08-22 10:49:51.889: E/AndroidRuntime(31697): at java.lang.reflect.Method.invoke(Method.java:511)
08-22 10:49:51.889: E/AndroidRuntime(31697): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
08-22 10:49:51.889: E/AndroidRuntime(31697): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
08-22 10:49:51.889: E/AndroidRuntime(31697): at dalvik.system.NativeStart.main(Native Method)
08-22 10:49:51.889: E/AndroidRuntime(31697): Caused by: android.view.InflateException: Binary XML file line #67: Error inflating class <unknown>
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.createView(LayoutInflater.java:606)
08-22 10:49:51.889: E/AndroidRuntime(31697): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.onCreateView(LayoutInflater.java:653)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:678)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.rInflate(LayoutInflater.java:739)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
08-22 10:49:51.889: E/AndroidRuntime(31697): at klick.beatbleeds.ActivityBase.setContentView(ActivityBase.java:82)
08-22 10:49:51.889: E/AndroidRuntime(31697): at klick.beatbleeds.Bleeds.onCreate(Bleeds.java:40)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.Activity.performCreate(Activity.java:4465)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1919)
08-22 10:49:51.889: E/AndroidRuntime(31697): ... 11 more
08-22 10:49:51.889: E/AndroidRuntime(31697): Caused by: java.lang.reflect.InvocationTargetException
08-22 10:49:51.889: E/AndroidRuntime(31697): at java.lang.reflect.Constructor.constructNative(Native Method)
08-22 10:49:51.889: E/AndroidRuntime(31697): at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.LayoutInflater.createView(LayoutInflater.java:586)
08-22 10:49:51.889: E/AndroidRuntime(31697): ... 23 more
08-22 10:49:51.889: E/AndroidRuntime(31697): Caused by: java.lang.OutOfMemoryError
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.Bitmap.nativeCreate(Native Method)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.Bitmap.createBitmap(Bitmap.java:605)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.Bitmap.createBitmap(Bitmap.java:551)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.Bitmap.createScaledBitmap(Bitmap.java:437)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.BitmapFactory.finishDecode(BitmapFactory.java:524)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:499)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:351)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:773)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.content.res.Resources.loadDrawable(Resources.java:1937)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.View.<init>(View.java:2780)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.view.ViewGroup.<init>(ViewGroup.java:385)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.widget.LinearLayout.<init>(LinearLayout.java:174)
08-22 10:49:51.889: E/AndroidRuntime(31697): at android.widget.LinearLayout.<init>(LinearLayout.java:170)
08-22 10:49:51.889: E/AndroidRuntime(31697): ... 26 more
这是其中一个 View 的屏幕截图,以了解此处使用了多少图像
最佳答案
使用这些静态方法找出确切的问题:
public static void showBitmapSize(Bitmap bitmap) {
Log.d("test", "bitmap dimensions: w:" + bitmap.getWidth() + ", h:" + bitmap.getHeight() + " memory: " + (bitmap.getRowBytes() * bitmap.getHeight() / 1048576d));
}
最重要的是:
static double lastavail;
static double initavail;
static boolean first = true;
public static void showMemoryStats() {
showMemoryStats("");
}
public static void showMemoryStats(String message) {
Log.i("memory", message + "----------------------------------------------------------------------------------------");
double nativeUsage = Debug.getNativeHeapAllocatedSize();
Log.i("memory", "nativeUsage: " + (nativeUsage / 1048576d));
//current heap size
double heapSize = Runtime.getRuntime().totalMemory();
// Log.i("memory", "heapSize: " + (heapSize / 1048576d));
//amount available in heap
double heapRemaining = Runtime.getRuntime().freeMemory();
// Log.i("memory", "heapRemaining: " + (heapRemaining / 1048576d));
double memoryAvailable = Runtime.getRuntime().maxMemory() - (heapSize - heapRemaining) - nativeUsage;
Log.i("memory", "memoryAvailable: " + (memoryAvailable / 1048576d));
if (first) {
initavail = memoryAvailable;
first = false;
}
if (lastavail > 0) {
Log.i("memory", "consumed since last: " + ((lastavail - memoryAvailable) / 1048576d));
}
Log.i("memory", "consumed total: " + ((initavail - memoryAvailable) / 1048576d));
lastavail = memoryAvailable;
Log.i("memory", "-----------------------------------------------------------------------------------------------");
}
除以 1048576 只是为了得到以 MB 为单位的值(至少对我来说,以 MB 为单位更容易思考)。
在 setContentView()
调用之前用一些有意义的消息调用 showMemoryStats
,在它之后调用另一个。当您开始一项新 Activity 时,等等。最后您将了解问题的确切原因。
可能需要手动回收。我必须在我的应用程序的某些地方实现它。还使用位图密集型(许多背景和图片)并且在所有设备中都存在此类问题。通过这些方法,我能够找到所有问题并妥善处理。
啊。并且您的问题可能有快速解决方案,您说它只出现在 Galaxy Nexus 中。这是您提到的唯一 xhdpi 设备。 您可能只在文件夹 drawable 或 drawable-hdpi 中拥有所有位图。 xhdpi 设备将从 drawable 或 drawable-hdpi 获取位图并放大(尽管它们可能已经处于正确的大小),这将消耗大量内存。解决方案:创建 drawable-xhdpi 文件夹(如果不存在),然后将位图的副本放在那里。
关于java - OutOfMemoryError 创建位图,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/12076422/