Out of memory running debug mode on Android

Expo Development Tools
1

In order to debug, I’ve activated debug mode on Expo client (sdk35 app) with react-native-debugger

Expo CLI 3.11.9 environment info:
    System:
      OS: macOS 10.14.6
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 13.5.0 - /usr/local/bin/node
      Yarn: 1.21.1 - /usr/local/bin/yarn
      npm: 6.12.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5692245
      Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
    npmPackages:
      @bugsnag/expo: 6.4.1 => 6.4.1
      @types/react: ^16.9.11 => 16.9.19
      @types/react-native: ^0.57.65 => 0.57.65
      expo: ^35.0.1 => 35.0.1
      react: 16.8.3 => 16.8.3
      react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
      react-navigation: 3.11.1 => 3.11.1
    npmGlobalPackages:
      expo-cli: 3.11.9

Here is the error catched by adb logcat

02-12 10:03:50.814 12699 13112 W st.exp.exponen: Throwing OutOfMemoryError with VmSize 43394496 kB "Failed to allocate a 83884872 byte allocation with 25165824 free bytes and 25MB until OOM, max allowed footprint 534784552, growth limit 536870912"
--------- beginning of crash
02-12 10:03:50.894 12699 13112 E AndroidRuntime: FATAL EXCEPTION: mqt_js
02-12 10:03:50.894 12699 13112 E AndroidRuntime: Process: host.exp.exponent, PID: 12699
02-12 10:03:50.894 12699 13112 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 83884872 byte allocation with 25165824 free bytes and 25MB until OOM, max allowed footprint 534784552, growth limit 536870912
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at libcore.util.CharsetUtils.toUtf8Bytes(Native Method)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at java.lang.String.getBytes(String.java:946)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at k.f.d(ByteString.java:1)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at okhttp3.internal.ws.RealWebSocket.send(RealWebSocket.java:1)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.devsupport.JSDebuggerWebSocketClient.sendMessage(JSDebuggerWebSocketClient.java:3)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.devsupport.JSDebuggerWebSocketClient.executeJSCall(JSDebuggerWebSocketClient.java:10)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.devsupport.WebsocketJavaScriptExecutor.executeJSCall(WebsocketJavaScriptExecutor.java:2)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:891)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:1)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:207)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at abi35_0_0.com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:8)
02-12 10:03:50.894 12699 13112 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:784)

It crashes with a real device and simulator.
Without JS remote debug mode, it works fine.