目录

未捕获JS-Crash异常导致应用崩溃该如何处理

问题现象

应用运行过程中可能会出现JS crash异常，当出现未被捕获的JS crash异常时应用崩溃。如下图：

背景知识

ErrorManager模块提供对错误观察器的注册和注销的能力，在EntryAbility中配置即可实现统一处理（目前taskpool中不支持捕获异常）。

解决方案

  1. 手动try-catch。

    针对出现异常的代码段手动try-catch捕获异常：

    error:  TypeError: Get Property index out-of-bounds
    import { ArrayList } from '@kit.ArkTS';

@Entry
@Component
struct Index {

  build() {
    Row() {
      Column() {
        Button('Hello World')
          .fontSize(50)
          .fontWeight(FontWeight.Bold)
          .onClick(() => {
            this.testClick();
          });
      }
      .width('100%');
    }
    .height('100%');
  }

  doublePages = new ArrayList<number>();

  testClick() {
    try {
      let i: number = this.doublePages[1]; // index out-of-bounds
      console.info(`i is ${i}`);
    } catch (e) {
      console.error('error: ', e);
    }
  }
}
  2. ErrorManager模块统一捕获。
    虽然通过try-catch能捕获异常，但整体方案仍然存在一定缺陷，比如添加大量try-catch导致可读性变差、遗漏JS Crash未被捕获。因此建议通过ErrorManager模块统一捕获未知JS Crash。
    import { ConfigurationConstant, errorManager, UIAbility } from '@kit.AbilityKit';
import { hilog } from '@kit.PerformanceAnalysisKit';
import { window } from '@kit.ArkUI';
import { BusinessError } from '@kit.BasicServicesKit';

const DOMAIN = 0x0000;
let observerId = -1;

export default class EntryAbility extends UIAbility {
  onCreate(): void {
    let observer1: errorManager.ErrorObserver = {
      onUnhandledException(errorMsg) {
        console.error('onUnhandledException, errorMsg: ', errorMsg);
      },
      onException(errorObj) {
        console.error('onException, name: ', errorObj.name);
        console.error('onException, message: ', errorObj.message);
        if (typeof (errorObj.stack) === 'string') {
          console.error('onException, stack: ', errorObj.stack);
        }
      }
    };
    try {
      // 注册错误观测器。注册后可以捕获到应用产生的js crash，应用崩溃时进程不会退出。
      observerId = errorManager.on('error', observer1);
    } catch (paramError) {
      let code = (paramError as BusinessError).code;
      let message = (paramError as BusinessError).message;
      console.error(`error: ${code}, ${message}`);
    }
    try {
      this.context.getApplicationContext().setColorMode(ConfigurationConstant.ColorMode.COLOR_MODE_NOT_SET);
    } catch (err) {
      hilog.error(DOMAIN, 'testTag', 'Failed to set colorMode. Cause: %{public}s', JSON.stringify(err));
    }
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onCreate');
  }

  onDestroy(): void {
    try {
      errorManager.off('error', observerId)
        .then((data) => {
          console.info('----------- unregisterErrorObserver success ----------', data);
        })
        .catch((err: BusinessError) => {
          console.error('----------- unregisterErrorObserver fail ----------', err);
        });
    } catch (paramError) {
      let code = (paramError as BusinessError).code;
      let message = (paramError as BusinessError).message;
      console.error(`error: ${code}, ${message}`);
    }
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onDestroy');
  }

  onWindowStageCreate(windowStage: window.WindowStage): void {
    // Main window is created, set main page for this ability
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onWindowStageCreate');

    windowStage.loadContent('pages/Index', (err) => {
      if (err.code) {
        hilog.error(DOMAIN, 'testTag', 'Failed to load the content. Cause: %{public}s', JSON.stringify(err));
        return;
      }
      hilog.info(DOMAIN, 'testTag', 'Succeeded in loading the content.');
    });
  }

  onWindowStageDestroy(): void {
    // Main window is destroyed, release UI related resources
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onWindowStageDestroy');
  }

  onForeground(): void {
    // Ability has brought to foreground
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onForeground');
  }

  onBackground(): void {
    // Ability has back to background
    hilog.info(DOMAIN, 'testTag', '%{public}s', 'Ability onBackground');
  }
};

    运行效果：出现JS Crash问题时应用无闪退并在日志中记录堆栈。