Chrome web browser memory leak Chrome Facebook using Leakcanary

By chance I have these leaks after doing login with Facebook

Webview

enter image description hereenter image description hereenter image description here

I found this (only mentioned in com.android.org.chromium

):

AW_RESOURCE__SRESOURCES(SAMSUNG.equals(MANUFACTURER) && SDK_INT == KITKAT) {
    @Override void add(ExcludedRefs.Builder excluded) {
      // AwResource#setResources() is called with resources that hold a reference to the
      // activity context (instead of the application context) and doesn't clear it.
      // Not sure what going on there, input welcome.
      excluded.staticField("com.android.org.chromium.android_webview.AwResource", "sResources");
    }
  },

      

Inside this class AndroidExcludedRefs.java

This class is incomplete. You can help by reporting the leaked traces that appear to be caused by the Android SDK here: https://github.com/square/leakcanary/issues/new

But I am not using Samsung, so I still have this leak.
Said this leak is known? Can you ignore it?

UPDATE: I was using Facebook SDK v3.19, I updated to 4.3 but the problem remains: enter image description here

+3


source to share


2 answers


So, I was in contact with facebook support center and we came to the conclusion:



Your intuition was correct. It seems to be a bug in chrome, not our SDK. It should be fixed in later versions of android as it was fixed in April this year.

See: https://code.google.com/p/chromium/issues/detail?id=478719

+1


source


Several memory leak fixes have been fixed in the latest versions of the Facebook SDK. Make sure you download the latest version (v4.3 for now).



+1


source







All Articles