Android内存泄漏分析及检测工具LeakCanary简介

  1. View

  2. Service

fun appDefaultWatchers(

application: Application,

reachabilityWatcher: ReachabilityWatcher = objectWatcher

): List {

return listOf(

ActivityWatcher(application, reachabilityWatcher),

FragmentAndViewModelWatcher(application, reachabilityWatcher),

RootViewWatcher(reachabilityWatcher),

ServiceWatcher(reachabilityWatcher)

)

}

首先我们来看一下ObjectWatcher ,它的关键代码如下:

@Synchronized fun watch(

watchedObject: Any,

description: String

) {

if (!isEnabled()) {

return

}

removeWeaklyReachableObjects()

val key = UUID.randomUUID()

.toString()

val watchUptimeMillis = clock.uptimeMillis()

val reference =

KeyedWeakReference(watchedObject, key, description, watchUptimeMillis, queue)

SharkLog.d {

"Watching " +

(if (watchedObject is Class<*>) watchedObject.toString() else “instance of ${watchedObject.javaClass.name}”) +

(if (description.isNotEmpty()) " ($description)" else “”) +

" with key $key"

}

watchedObjects[key] = reference

checkRetainedExecutor.execute {

moveToRetained(key)

}

}

主要是对watchedObject使用了弱引用,同时注意到里面使用了ReferenceQueue,这两者结合使用可以实现如果弱引用关联的对象被回收,就会把这个弱引用加入到queue中,以此来判断该对象是否被回收。

LeakCanary主要的检测对象是以上4种,以Activity为例进行分析,其他检测类型也是类似原理,不再赘述。

class ActivityWatcher(

private val application: Application,

private val reachabilityWatcher: ReachabilityWatcher

) : InstallableWatcher {

private val lifecycleCallbacks =

object : Application.ActivityLifecycleCallbacks by noOpDelegate() {

override fun onActivityDestroyed(activity: Activity) {

reachabilityWatcher.expectWeaklyReachable(

activity, “${activi

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值