Zoom is leaking memory

Describe the bug
After the fragment is destroyed the application does not properly destroy the instances causing a leak (can cause an OutOfMemoryError).

Which version?

To Reproduce
Steps to reproduce the behavior:

  1. Copy and paste ZoomVideocall.java inside your application
  2. Inside a fragment through any ui interface (like a button) start the class using the following functions:
	private ZoomVideocall mVideocall;

    private void startVideocall() {
        if(mVideocall == null) {
            mVideocall = new ZoomVideocall(requireContext());

  1. Add onDestroyView()
    public void onDestroyView() {
  1. Now check with LeakCanary the leak produced.

Expected behavior
Should not leak.


Smartphone (please complete the following information):

  • Device: OnePlus Nord

Additional context

  • Build.VERSION.SDK_INT: 29
  • LeakCanary version: 2.5

Hi @alphadevgroup, thanks for using our SDK.

Thank you for catching this memory leak. I was able to reproduce this quite easily, and confirmed that it does not require copying over your ZoomVideocall class. We will investigate this and let you know as soon as we have an update.


1 Like