Android内存优化8 内存检测工具2 LeakCanary——直白的展现Android中的内存泄露
Android内存优化8 内存检测工具2 LeakCanary——直白的展现Android中的内存泄露
之前碰到的OOM问题,终于很直白的呈现在我的眼前:我尝试了MAT,但是发现不怎么会用。直到今天终于发现了这个新工具:
当我们的App中存在内存泄露时会在通知栏弹出通知:
当点击该通知时,会跳转到具体的页面,展示出Leak的引用路径,如下图所示:
LeakCanary 可以用更加直白的方式将内存泄露展现在我们的面前。
工程包括:
- LeakCanary库代码
- LeakCanaryDemo示例代码
使用步骤:
- 将LeakCanary import 入自己的工程
- 添加依赖:
compile project(':leakcanary')
- 在Application中进行配置
public class ExampleApplication extends Application { ...... //在自己的Application中添加如下代码 public static RefWatcher getRefWatcher(Context context) { ExampleApplication application = (ExampleApplication) context .getApplicationContext(); return application.refWatcher; } //在自己的Application中添加如下代码 private RefWatcher refWatcher; @Override public void onCreate() { super.onCreate(); ...... //在自己的Application中添加如下代码 refWatcher = LeakCanary.install(this); ...... } ..... }
- 在Activity中进行配置
public class MainActivity extends AppCompatActivity {
......
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
//在自己的应用初始Activity中加入如下两行代码
RefWatcher refWatcher = ExampleApplication.getRefWatcher(this);
refWatcher.watch(this);
textView = (TextView) findViewById(R.id.tv);
textView.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
startAsyncTask();
}
});
}
private void async() {
startAsyncTask();
}
private void startAsyncTask() {
// This async task is an anonymous class and therefore has a hidden reference to the outer
// class MainActivity. If the activity gets destroyed before the task finishes (e.g. rotation),
// the activity instance will leak.
new AsyncTask<Void, Void, Void>() {
@Override
protected Void doInBackground(Void... params) {
// Do some slow work in background
SystemClock.sleep(20000);
return null;
}
}.execute();
}
}
- 在AndroidMainfest.xml 中进行配置,添加如下代码
<service
android:name="com.squareup.leakcanary.internal.HeapAnalyzerService"
android:enabled="false"
android:process=":leakcanary" />
<service
android:name="com.squareup.leakcanary.DisplayLeakService"
android:enabled="false" />
<activity
android:name="com.squareup.leakcanary.internal.DisplayLeakActivity"
android:enabled="false"
android:icon="@drawable/__leak_canary_icon"
android:label="@string/__leak_canary_display_activity_label"
android:taskAffinity="com.squareup.leakcanary"
android:theme="@style/__LeakCanary.Base" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
5、测试结果
a、Toast显示(大概10秒左右显示)
b、通知显示
c、桌面自动添加的图表
d、内存泄露列表
e、内存泄露详细
LogCat可以看到日志日下(hprof文件可以用MAT打开进行分析):
- 01-04 11:49:41.815 12967-13004/com.micky.leakcanarysamples I/dalvikvm: hprof: dumping heap strings to “/storage/emulated/0/Download/leakcanary/suspected_leak_heapdump.hprof”.
- 01-04 11:49:42.020 12967-13004/com.micky.leakcanarysamples I/dalvikvm: hprof: heap dump completed (28850KB)
查看自动生成的AndroidManifest文件,LeakCanarySamples/app/build/intermediates/manifests/full/debug/AndroidManifest.xml
- <?xml version=“1.0” encoding=”utf-8″?>
- <manifest xmlns:android=“http://schemas.android.com/apk/res/android”
- package=“com.micky.leakcanarysamples”
- android:versionCode=“1”
- android:versionName=“1.0” >
- <uses-sdk
- android:minSdkVersion=“10”
- android:targetSdkVersion=“23” />
- <!– To store the heap dumps and leak analysis results. –>
- <uses-permission android:name=“android.permission.WRITE_EXTERNAL_STORAGE” />
- <android:uses-permission android:name=“android.permission.READ_EXTERNAL_STORAGE” />
- <application
- android:name=“com.micky.leakcanarysamples.BaseApplication”
- android:allowBackup=“true”
- android:icon=“@mipmap/ic_launcher”
- android:label=“@string/app_name”
- android:supportsRtl=“true”
- android:theme=“@style/AppTheme” >
- <activity
- android:name=“com.micky.leakcanarysamples.MainActivity”
- android:label=“@string/app_name”
- android:theme=“@style/AppTheme.NoActionBar” >
- <intent-filter>
- <action android:name=“android.intent.action.MAIN” />
- <category android:name=“android.intent.category.LAUNCHER” />
- </intent-filter>
- </activity>
- <activity android:name=“com.micky.leakcanarysamples.TestActivity” />
- <service
- android:name=“com.squareup.leakcanary.internal.HeapAnalyzerService”
- android:enabled=“false”
- android:process=“:leakcanary” />
- <service
- android:name=“com.squareup.leakcanary.DisplayLeakService”
- android:enabled=“false” />
- <activity
- android:name=“com.squareup.leakcanary.internal.DisplayLeakActivity”
- android:enabled=“false”
- android:icon=“@drawable/__leak_canary_icon”
- android:label=“@string/__leak_canary_display_activity_label”
- android:taskAffinity=“com.squareup.leakcanary”
- android:theme=“@style/__LeakCanary.Base” >
- <intent-filter>
- <action android:name=“android.intent.action.MAIN” />
- <category android:name=“android.intent.category.LAUNCHER” />
- </intent-filter>
- </activity>
- </application>
- </manifest>
如上所示LeakCanary给我们自动添加了两个Service和一个Activity,并添加了对SD卡的读写权限
It 's so simple.
注:
1、如果在Release模式下请使用RefWatcher.DISABLED
2、在Activity或Fragment 的 Destroy方法中添加检测(很好理解,就是判断一个Activity或Fragment想要被销毁的时候,是否还有其他对象持有其引用导致Activity或Fragment不能被回收,从而导致内存泄露)