深入理解 Android 9.0 Crash 机制读懂底层原理看清表面逻辑( 四 ) _Android

5.1 handleAppCrashInActivityController
handleAppCrashInActivityController,通过IActivityController 实例导致的Crash ，则不显示弹窗.
AppError.java
private boolean handleAppCrashInActivityController(ProcessRecord r, ApplicationErrorReport.CrashInfo crashInfo, String shortMsg, String longMsg, String stackTrace, long timeMillis, int callingPid, int callingUid) { ... ...// 当存在ActivityController的情况,比如monkey try { String name = r != null ? r.processName : null; int pid = r != null ? r.pid : callingPid; int uid = r != null ? r.info.uid : callingUid; //调用monkey的 appCrashed if (!mService.mController.appCrashed(name, pid, shortMsg, longMsg, timeMillis, crashInfo.stackTrace)) { if ("1".equals(SystemProperties.get(SYSTEM_DEBUGGABLE, "0")) && "Native crash".equals(crashInfo.exceptionClassName)) { Slog.w(TAG, "Skip killing native crashed app " + name + "(" + pid + ") during testing"); } else { Slog.w(TAG, "Force-killing crashed app " + name + " at watcher's request"); if (r != null) { //调用`makeAppCrashingLocked` ，继续处理crash流程 // 详见小结 6if (!makeAppCrashingLocked(r, shortMsg, longMsg, stackTrace, null)) { r.kill("crash", true); } } else { // Huh. Process.killProcess(pid); ActivityManagerService.killProcessGroup(uid, pid); } } return true; } } catch (RemoteException e) { mService.mController = null; Watchdog.getInstance().setActivityController(null); } return false; }该方法主要做的两件事：

调用makeAppCrashingLocked ，继续处理Crash流程；
发送消息SHOW_ERROR_MSG ，弹出提示Crash的对话框，等待用户选择；
接下来我们看makeAppCrashingLocked实现。

六、makeAppCrashingLocked处理分析AppError.java
private boolean makeAppCrashingLocked(ProcessRecord app, String shortMsg, String longMsg, String stackTrace, AppErrorDialog.Data data) { app.crashing = true; //封装crash信息到crashingReport对象 app.crashingReport = generateProcessError(app, ActivityManager.ProcessErrorStateInfo.CRASHED, null, shortMsg, longMsg, stackTrace); //【见小节7】 startAppProblemLocked(app); //停止屏幕冻结【见小节8】 app.stopFreezingAllLocked(); //【见小节9】 return handleAppCrashLocked(app, "force-crash" /*reason*/, shortMsg, longMsg, stackTrace, data); }七、startAppProblemLocked处理分析AppError.java
startAppProblemLocked 该方法主要功能：

获取当前用户下的crash应用的error receiver；
忽略当前App的广播接收；

void startAppProblemLocked(ProcessRecord app) { // 如果不是当前user正在运行 app ，这置为空 app.errorReportReceiver = null; for (int userId : mService.mUserController.getCurrentProfileIds()) { if (app.userId == userId) { //获取当前用户下的crash应用的error receiver【见小节7.1】 app.errorReportReceiver = ApplicationErrorReport.getErrorReportReceiver( mContext, app.info.packageName, app.info.flags); } } //忽略当前app的广播接收【见小节7.2】 mService.skipCurrentReceiverLocked(app); }7.1 getErrorReportReceiver
ApplicationErrorReport.java
获取当前用户下的Crash应用的error receiver
public static ComponentName getErrorReportReceiver(Context context, String packageName, int appFlags) { //检查Settings中的"send_action_app_error"是否使能错误报告的功能 int enabled = Settings.Global.getInt(context.getContentResolver(), Settings.Global.SEND_ACTION_APP_ERROR, 0); if (enabled == 0) { //1.当未使能时，则直接返回 return null; } PackageManager pm = context.getPackageManager(); // look for receiver in the installer package String candidate = null; ComponentName result = null; try { //获取该crash应用的安装器的包名 candidate = pm.getInstallerPackageName(packageName); } catch (IllegalArgumentException e) { // the package could already removed } if (candidate != null) { result = getErrorReportReceiver(pm, packageName, candidate); if (result != null) { //2.当找到该crash应用的安装器，则返回； return result; } } //该系统属性名为"ro.error.receiver.system.apps" if ((appFlags&ApplicationInfo.FLAG_SYSTEM) != 0) { candidate = SystemProperties.get(SYSTEM_APPS_ERROR_RECEIVER_PROPERTY); // 通过上下文对象传参，调用类内部方法 result = getErrorReportReceiver(pm, packageName, candidate); if (result != null) { //3.当crash应用是系统应用时，且系统属性指定error receiver时，则返回； return result; } } //该默认属性名为"ro.error.receiver.default" candidate = SystemProperties.get(DEFAULT_ERROR_RECEIVER_PROPERTY); //4.当默认属性值指定error receiver时，则返回； return getErrorReportReceiver(pm, packageName, candidate); }getErrorReportReceiver：这是同名不同输入参数的另一个方法：