LeakCanary 报告 InputMethodManager 中的泄漏

Question

我正在尝试找出我的应用程序中的泄漏，但我不确定这是来自哪里。

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

Answer 1

是的，你可以忽略这个泄漏。

检查例如这个问题：https://github.com/square/leakcanary/issues/256

Answer 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();
        }
    }
}

Answer 3

是的，您可以忽略此泄漏。解决上述泄漏的 hacky 解决方案适用于所有版本是 here

---

2022 年 4 月编辑：-

中等故事的作者删除了它但the solution was around using a transparent activity as an exit activity.

Answer 4

LeakCanary 已经将此泄漏视为 Android 操作系统故障。但仍然发生，这让我很恼火。如果有人遇到此问题并想修复它，则有一种解决方法。

https://gist.github.com/pyricau/4df64341cc978a7de414

只需调用 Activity 的 onCreate 这个

IMMLeaks.fixFocusedViewLeak(getApplication());