瀏覽代碼

android: fix deadlock in uncaught exception handler

The app is about to crash at that stage so it was a moot point to try to leave
the conference anyway.

Stopping ConnectionServers is still a good idea though, since a crash may leave
the device in a bad state otherwise.
master
Saúl Ibarra Corretgé 5 年之前
父節點
當前提交
d2c85ada1b
共有 1 個文件被更改,包括 0 次插入7 次删除
  1. 0
    7
      android/sdk/src/main/java/org/jitsi/meet/sdk/JitsiMeetUncaughtExceptionHandler.java

+ 0
- 7
android/sdk/src/main/java/org/jitsi/meet/sdk/JitsiMeetUncaughtExceptionHandler.java 查看文件

39
     public void uncaughtException(Thread t, Throwable e) {
39
     public void uncaughtException(Thread t, Throwable e) {
40
         Log.e(this.getClass().getSimpleName(), "FATAL ERROR", e);
40
         Log.e(this.getClass().getSimpleName(), "FATAL ERROR", e);
41
 
41
 
42
-        // Terminate all conferences
43
-        for (BaseReactView view: BaseReactView.getViews()) {
44
-            if (view instanceof JitsiMeetView) {
45
-                ((JitsiMeetView) view).leave();
46
-            }
47
-        }
48
-
49
         // Abort all ConnectionService ongoing calls
42
         // Abort all ConnectionService ongoing calls
50
         if (AudioModeModule.useConnectionService()) {
43
         if (AudioModeModule.useConnectionService()) {
51
             ConnectionService.abortConnections();
44
             ConnectionService.abortConnections();

Loading…
取消
儲存