Android Chrome Facebook webview 内存泄漏使用 Leakcanary
Android Chrome Facebook webview memory leak using Leakcanary
我在使用 Facebook
Webview
执行登录后随机遇到此泄漏
我找到了这个(唯一提到 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's going on there, input welcome.
excluded.staticField("com.android.org.chromium.android_webview.AwResource", "sResources");
}
},
里面这个classAndroidExcludedRefs.java
This class is a work in progress. You can help by reporting leak
traces that seem to be caused by the Android SDK, here:
https://github.com/square/leakcanary/issues/new
但我没有使用三星,所以我仍然遇到这个问题。
话说,这个泄漏是一个已知问题吗?可以忽略吗?
更新: 我使用的是 Facebook SDK v3.19,我已经更新到 4.3,但问题仍然存在:
最新版本的 Facebook SDK 中修复了一些内存泄漏问题。确保下载最新版本(截至目前为 v4.3)。
所以我一直在联系 facebook 支持中心,我们得出的结论是:
Your intuition was correct. This seems to be a bug in chrome and not
our SDK. It should be fixed in later versions of android since it was
fixed in April of this year.
See: https://code.google.com/p/chromium/issues/detail?id=478719
我在使用 Facebook
Webview
我找到了这个(唯一提到 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's going on there, input welcome.
excluded.staticField("com.android.org.chromium.android_webview.AwResource", "sResources");
}
},
里面这个classAndroidExcludedRefs.java
This class is a work in progress. You can help by reporting leak traces that seem to be caused by the Android SDK, here: https://github.com/square/leakcanary/issues/new
但我没有使用三星,所以我仍然遇到这个问题。
话说,这个泄漏是一个已知问题吗?可以忽略吗?
更新: 我使用的是 Facebook SDK v3.19,我已经更新到 4.3,但问题仍然存在:
最新版本的 Facebook SDK 中修复了一些内存泄漏问题。确保下载最新版本(截至目前为 v4.3)。
所以我一直在联系 facebook 支持中心,我们得出的结论是:
Your intuition was correct. This seems to be a bug in chrome and not our SDK. It should be fixed in later versions of android since it was fixed in April of this year.
See: https://code.google.com/p/chromium/issues/detail?id=478719