android原理分析博客,Android WatchDog原理分析

最新推荐文章于 2024-06-20 16:20:13 发布

久立

最新推荐文章于 2024-06-20 16:20:13 发布

阅读量294

点赞数

文章标签： android原理分析博客

简述

了解WatchDog的原理，可以更好的理解系统服务的运行机制

分析

1.Watchdog extends Thread

Watchdog是一个线程

2.在SystemServer.java中启动

private void startOtherServices() {

······

traceBeginAndSlog("InitWatchdog");

final Watchdog watchdog = Watchdog.getInstance();

watchdog.init(context, mActivityManagerService);

traceEnd();

······

traceBeginAndSlog("StartWatchdog");

Watchdog.getInstance().start();

traceEnd();

}

因为是线程，所以，只要start即可

3.查看WatchDog的构造方法

private Watchdog() {

super("watchdog");

// Initialize handler checkers for each common thread we want to check. Note

// that we are not currently checking the background thread, since it can

// potentially hold longer running operations with no guarantees about the timeliness

// of operations there.

// The shared foreground thread is the main checker. It is where we

// will also dispatch monitor checks and do other work.

mMonitorChecker = new HandlerChecker(FgThread.getHandler(),

"foreground thread", DEFAULT_TIMEOUT);

mHandlerCheckers.add(mMonitorChecker);

// Add checker for main thread. We only do a quick check since there

// can be UI running on the thread.

mHandlerCheckers.add(new HandlerChecker(new Handler(Looper.getMainLooper()),

"main thread", DEFAULT_TIMEOUT));

// Add checker for shared UI thread.

mHandlerCheckers.add(new HandlerChecker(UiThread.getHandler(),

"ui thread", DEFAULT_TIMEOUT));

// And also check IO thread.

mHandlerCheckers.add(new HandlerChecker(IoThread.getHandler(),

"i/o thread", DEFAULT_TIMEOUT));

// And the display thread.

mHandlerCheckers.add(new HandlerChecker(DisplayThread.getHandler(),

"display thread", DEFAULT_TIMEOUT));

// Initialize monitor for Binder threads.

addMonitor(new BinderThreadMonitor());

mOpenFdMonitor = OpenFdMonitor.create();

// See the notes on DEFAULT_TIMEOUT.

assert DB ||

DEFAULT_TIMEOUT > ZygoteConnectionConstants.WRAPPED_PID_TIMEOUT_MILLIS;

// mtk enhance

exceptionHWT = new ExceptionLog();

}

1.重点关注两个对象：mMonitorChecker和mHandlerCheckers

2.mHandlerCheckers列表元素的来源：

1)构造对象的导入：UiThread、IoThread、DisplatyThread、FgThread加入

2)外部导入：Watchdog.getInstance().addThread(handler);

3.mMonitorChecker列表元素的来源：

外部导入：Watchdog.getInstance().addMonitor(monitor);

特别说明：addMonitor(new BinderThreadMonitor());

4.查看WatchDog的run方法

public void run() {

boolean waitedHalf = false;

boolean mSFHang = false;

while (true) {

······

synchronized (this) {

······

for (int i=0; i

HandlerChecker hc = mHandlerCheckers.get(i);

hc.scheduleCheckLocked();

}

······

}

······

}

对mHandlerCheckers列表元素进行检测

5.查看HandlerChecker的scheduleCheckLocked

public void scheduleCheckLocked() {

if (mMonitors.size() == 0 && mHandler.getLooper().getQueue().isPolling()) {

// If the target looper has recently been polling, then

// there is no reason to enqueue our checker on it since that

// is as good as it not being deadlocked. This avoid having

// to do a context switch to check the thread. Note that we

// only do this if mCheckReboot is false and we have no

// monitors, since those would need to be executed at this point.

mCompleted = true;

return;

}

if (!mCompleted) {

// we already have a check in flight, so no need

return;

}

mCompleted = false;

mCurrentMonitor = null;

mStartTime = SystemClock.uptimeMillis();

mHandler.postAtFrontOfQueue(this);

}

1.mMonitors.size() == 0的情況，

主要为了检查mHandlerCheckers中的元素是否超时，运用的手段：mHandler.getLooper().getQueue().isPolling()

2.mMonitorChecker对象的列表元素一定是大于0，此时，关注点在mHandler.postAtFrontOfQueue(this)：

public void run() {

final int size = mMonitors.size();

for (int i = 0 ; i < size ; i++) {

synchronized (Watchdog.this) {

mCurrentMonitor = mMonitors.get(i);

}

mCurrentMonitor.monitor();

}

synchronized (Watchdog.this) {

mCompleted = true;

mCurrentMonitor = null;

}

运用的手段：监听monitor方法

1)这里是对mMonitors进行monitor,而能够满足条件的只有：mMonitorChecker,例如：各种服务通过addMonitor加入列表

ActivityManagerService.java