今天我们来分析下Activity的启动流程,看看Activity是啥时候创建的,窗口是啥时候创建的,Context呢?
我们启动一个Activity时一般是这样的:
Intent intent = new Intent(MainActivity.this, TestActivity.class);
startActivity(intent);
实际上startActivity调用的是Activity类里面的方法,在Activity类中startActivity有多个重载方法,但最后调用的都是startActivityForResult方法
public void startActivityForResult(@RequiresPermission Intent intent, int requestCode,
@Nullable Bundle options) {
//mParent代表的是ActivityGroup,肯定是null的
if (mParent == null) {
options = transferSpringboardActivityOptions(options);
Instrumentation.ActivityResult ar =
mInstrumentation.execStartActivity(
this, mMainThread.getApplicationThread(), mToken, this,
intent, requestCode, options);
if (ar != null) {
mMainThread.sendActivityResult(
mToken, mEmbeddedID, requestCode, ar.getResultCode(),
ar.getResultData());
}
if (requestCode >= 0) {
mStartedActivity = true;
}
cancelInputsAndStartExitTransition(options);
// TODO Consider clearing/flushing other event sources and events for child windows.
} else {
if (options != null) {
mParent.startActivityFromChild(this, intent, requestCode, options);
} else {
mParent.startActivityFromChild(this, intent, requestCode);
}
}
}
看上面的源码,这里需要注意的是这里会走mParent==null这个分支。mParent代表的是ActivityGroup,也就是一个Activity里面再嵌套Activity,这种方式已经被Fragment替代了。
这里的mMainThread就是ActivityThread,而mMainThread.getApplicationThread()就是ActivityThread的内部类ApplicationThread。ActivityThread和ApplicationThread在Activity的启动过程中发挥了很重要的作用。
//Instrumentation.class
public ActivityResult execStartActivity(
Context who, IBinder contextThread, IBinder token, Activity target,
Intent intent, int requestCode, Bundle options) {
//这里可以看到ApplicationThread其实是个Binder
IApplicationThread whoThread = (IApplicationThread) contextThread;
Uri referrer = target != null ? target.onProvideReferrer() : null;
if (referrer != null) {
intent.putExtra(Intent.EXTRA_REFERRER, referrer);
}
...
try {
intent.migrateExtraStreamToClipData();
intent.prepareToLeaveProcess(who);
//调用ActivityManagerNative的getDefault方法返回ActivityManagerService
int result = ActivityManagerNative.getDefault()
.startActivity(whoThread, who.getBasePackageName(), intent,
intent.resolveTypeIfNeeded(who.getContentResolver()),
token, target != null ? target.mEmbeddedID : null,
requestCode, 0, null, options);
//这个方法用于检查Activity的启动结果,如果启动失败是抛出相应的异常
checkStartActivityResult(result, intent);
} catch (RemoteException e) {
throw new RuntimeException("Failure from system", e);
}
return null;
}
从Instrumentation的execStartActivity源码可以看到,ApplicationThread其实是个Binder,它主要是供后面从ActivityManagerService的进程回调到应用的进程。同时启动Activity的过程通过Binder机制转到了ActivityManagerService。
ActivityManagerService中的Activity的启动过程就相对复杂很多,需要经过很多的跳转和处理,比如需要判断要启动的Activity的任务栈是否存在,不存在的话要创建任务栈;暂停当前的Activity,以便当前待启动的Activity可以获取焦点等。这里我们就不跟进去看源码了,容易绕晕。
ActivityManagerService做好自己的事儿以后,就会调用我们传过去的Binder对象ApplicationThread的scheduleLaunchActivity来将进程切换到当前应用的进程,以便继续完成启动Activity的任务。
//ApplicationThread.class
@Override
public final v