本文介绍了Android中Handler的内存泄漏问题及其解决方案——WeakHandler。Handler在默认实现时会保留对处理对象的硬引用，可能导致内存泄漏。WeakHandler通过保持对Runnable和Message的弱引用，解决了这一问题。当WeakHandler不再被引用时，GC可以回收相关资源。使用WeakHandler只需在构建文件中添加依赖，并像普通Handler一样使用。 WeakHandler由Badoo公司发布，遵循MIT许可证。
Android Weak Handler
Memory safer implementation of android.os.Handler
Problem
Original implementation of Handler always keeps hard reference to handler in queue of execution.
Any object in Message or Runnable posted to android.os.Handler will be hard referenced for some time.
If you create anonymous Runnable and call to postDelayed with large timeout, that Runnable will be held
in memory until timeout passes. Even if your Runnable seems small, it indirectly references owner class,
which is usually something as big as Activity or Fragment.
You can read more on our blog post.
Solution
WeakHandler is trickier then android.os.Handler , it will keep WeakReferences to runnables and messages,
and GC could collect them once WeakHandler instance is not referenced any more.
Usage
Add reference to your build.gradle:
repositories {
maven {
repositories {
url 'https://oss.sonatype.org/content/repositories/releases/'
}
}
}
dependencies {
compile 'com.badoo.mobile:android-weak-handler:1.1'
}
Use WeakHandler as you normally would use Handler
import com.badoo.mobile.util.WeakHandler;
public class ExampleActivity extends Activity {
private WeakHandler mHandler; // We still need at least one hard reference to WeakHandler
protected void onCreate(Bundle savedInstanceState) {
mHandler = new WeakHandler();
...
}
private void onClick(View view) {
mHandler.postDelayed(new Runnable() {
view.setVisibility(View.INVISIBLE);
}, 5000);
}
}
Credits
Weak Handler is brought to you by Badoo Trading Limited and it is released under the MIT License.
##Blog
Read more on our tech blog or explore our other open source projects
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
