我试图弄清楚我的应用程序中的漏洞,但我不确定这是否来自。
LeakCanary告诉我,我可以忽略它。是吗?
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * LEAK CAN BE IGNORED.
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * com.mypackage.ui.map.MapComponentFragment has leaked:
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * GC ROOT android.view.inputmethod.InputMethodManager$1.this$0 (anonymous class extends com.android.internal.view.IInputMethodClient$Stub)
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references android.view.inputmethod.InputMethodManager.mCurRootView
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references com.android.internal.policy.impl.PhoneWindow$DecorView.mContext
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references com.mypackage.ui.MainActivity.mFragments
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references android.app.FragmentManagerImpl.mAdded
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references java.util.ArrayList.array
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * references array java.lang.Object[].[0]
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * leaks com.mypackage.ui.map.MapComponentFragment instance
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * Reference Key: 0790f013-1c87-4d5f-8c10-db277187e3ce
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * Device: samsung samsung SM-N910C treltexx
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * Android Version: 5.1.1 API: 22 LeakCanary: 1.4-SNAPSHOT 2714152
01-06 12:04:56.580 6935-9159/com.mypackage D/LeakCanary: * Durations: watch=5085ms, gc=149ms, heap dump=2562ms, analysis=10313ms
这个碎片导致了几次泄漏,但我修复了它们。这个我不能让它消失。
有任何线索吗?
修改
还有一件事,如果我想忽略它,这应该足够了吗?
.instanceField("android.view.inputmethod.InputMethodManager", "mCurRootView")
但仍然出现在LeakCanary
显然这个漏洞在AndroidExcludeRef中,但仍在报告中。 https://github.com/square/leakcanary/issues/322
答案 0 :(得分:3)
是的,你可以忽略这个漏洞。
答案 1 :(得分:2)
/**
* call this method in activity onDestroy() method.
*/
public static void fixInputMethod(Context context) {
if (context == null) {
return;
}
InputMethodManager inputMethodManager = null;
try {
inputMethodManager = (InputMethodManager) context.getSystemService(Context.INPUT_METHOD_SERVICE);
} catch (Throwable th) {
th.printStackTrace();
}
if (inputMethodManager == null) {
return;
}
Field[] declaredFields = inputMethodManager.getClass().getDeclaredFields();
for (Field declaredField : declaredFields) {
try {
if (!declaredField.isAccessible()) {
declaredField.setAccessible(true);
}
Object obj = declaredField.get(inputMethodManager);
if (obj == null || !(obj instanceof View)) {
continue;
}
View view = (View) obj;
if (view.getContext() == context) {
declaredField.set(inputMethodManager, null);
} else {
continue;
}
} catch (Throwable th) {
th.printStackTrace();
}
}
}
答案 2 :(得分:1)
是的,你可以忽略这个泄漏但是毕竟,泄漏是一个不受欢迎的情况,我们应该尝试使用任何黑客或技巧来修复。
适用于所有版本的上述泄漏的优雅解决方案是here
答案 3 :(得分:0)
LeakCanary已将此漏洞视为Android操作系统故障。但仍然在发生,它让我恼火。如果有人进入此并希望修复它,则有一种解决方法。
https://gist.github.com/pyricau/4df64341cc978a7de414
只需调用此活动的onCreate
即可IMMLeaks.fixFocusedViewLeak(getApplication());