Consider to work around View leak in InputMethodManager (b.android.com/205171) in support lib [37122102]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

yu...@google.com

created issue #1

Oct 5, 2016 04:38AM

Even though the View leak

bug 36949180

is fixed in Android N, on older devices many Android apps that use Fragments are supposed to be still suffering from that bug.

It would be great if we can work around this bug somewhere in the support library so that app developers can easily avoid this issue just by updating the SDK and rebuild their apps.

Typical steps to reproduce this issue (if the app is suffering from

bug 36949180

)
1. Launch the app.
2. Hit the back button on the NavBar.
3. Wait for a while.

Expected behavior:
InputMethodManager#mServedView and InputMethodManager#mNextServedView should be null.

Actual behavior:
InputMethodManager#mServedView and/or InputMethodManager#mNextServedView still holds a strong reference to View object.

Comments

yu...@google.com <yu...@google.com> #2Nov 30, 2018 07:46PM

Yigit, do you have time to fix it?

reemission of the same liveData is racy

il...@google.com <il...@google.com> #3Dec 12, 2018 07:08PM

Marked as fixed.

yea i'll take it.

ma...@gmail.com <ma...@gmail.com> #4Aug 13, 2024 02:10AM

Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.

Issue 37122102

Description

Issue summary

Comments

yu...@google.com <yu...@google.com> #2Nov 30, 2018 07:46PM

il...@google.com <il...@google.com> #3Dec 12, 2018 07:08PM

ma...@gmail.com <ma...@gmail.com> #4Aug 13, 2024 02:10AM

Add comment

Issue metadata