Run following commands and enjoy the stream of warnings from Dokka:

rm -rf docs/api
./gradlew leakcanary-android-core:dokka leakcanary-android-instrumentation:dokka leakcanary-android-process:dokka leakcanary-object-watcher-android:dokka leakcanary-object-watcher:dokka shark-android:dokka shark-graph:dokka shark-hprof:dokka shark-log:dokka shark:dokka

Review errors and see if any of t

Here is a draft for what the best practices should contain. Follow-up of #18.

Topics

No console.log() on non-primitive values in tests

As @mjhea0 pointed out, the console.* methods will keep a reference to any object/array/function you pass them, thus artificially introducing a memory leak. See http://stackoverflow.com/a/28859493/1799408.

Leakage tests are quite slow

..

通过am start跳转到首页后，按2次返回并没有回到桌面，而是继续返回到之前的页面，这个时候去dump内存分析并不能说明是内存泄露，这个流程有更好的优化方案吗

Prerequisites

• I have written a descriptive issue title
• I have verified that I am running the latest version of DisposableFixer: 2.4.2
• I have searched open and closed issues to ensure it has not already been reported

Description