From 3dcc234efd8dc9f39588e11f2d4ea2ac8df34f39 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Felix=20Oghin=C4=83?= <foghina@fb.com>
Date: Fri, 2 Oct 2015 03:41:51 -0700
Subject: [PATCH] do not destroy instance when handling exception

Differential Revision: D2502513
---
 .../java/com/facebook/react/bridge/CatalystInstance.java   | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstance.java b/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstance.java
index be3cd5d0a..7314648df 100644
--- a/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstance.java
+++ b/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstance.java
@@ -355,13 +355,6 @@ public class CatalystInstance {
       // framework/native code, it was triggered by JS and theoretically since we were able
       // to set up the bridge, JS could change its logic, reload, and not trigger that crash.
       mNativeModuleCallExceptionHandler.handleException(e);
-      mCatalystQueueConfiguration.getUIQueueThread().runOnQueue(
-          new Runnable() {
-            @Override
-            public void run() {
-              destroy();
-            }
-          });
     }
   }