High amount of native memory remains allocated after leaving a call on Android

[mayn-and]

What happened?

What happened?

On Android, calling JitsiMeetView.dispose() (or equivalent cleanup) after leaving a meeting does not appear to fully destroy the React Native runtime. As a result, a significant amount of native memory remains allocated after the conference ends.

Based on the discussion, Android currently does not provide an API for allowing React Native instance to be destroyed.

For applications where meetings are infrequent (for example, one call per day), it would be useful to have an Android API that completely destroys the React Native instance after the meeting finishes, allowing the native memory used by React Native, Hermes, and associated modules to be reclaimed.

Platform

• Chrome (or Chromium based)
• Firefox
• Safari
• Other desktop browser
• Android browser
• iOS browser
• Electron app
• Android mobile app
• iOS mobile app
• Custom app using a mobile SDK

Browser / app / sdk version

13.1.0

Relevant log output

Reproducibility

• The problem is reproducible on meet.jit.si

More details?

Discussion took place here: https://community.jitsi.org/t/high-amount-of-native-memory-remains-allocated-after-leaving-a-call-on-android-and-ios/142468/15

dispose() on Android does not destroy the React Native runtime. An equivalent API on Android would need to be added.

[saghul]

@Calinteodor Let's add the APIs to destroy RN, like we do for iOS.