InputManager. mLateInitContext leak in Android U

[pyricau]

This leak was caught by the leak detection code that runs as part of the Android X test suite, yay!

LeakTrace information

Signature: 10c1a5aa4b18fa45418c2fd92d175e4813f38d80
┬───
│ GC Root: System class
│
├─ android.hardware.input.InputManager class
│    Leaking: NO (a class is never leaking)
│    ↓ static InputManager.sInstance
│                          ~~~~~~~~~
├─ android.hardware.input.InputManager instance
│    Leaking: UNKNOWN
│    Retaining 338.2 kB in 2514 objects
│    mLateInitContext instance of android.app.ContextImpl
│    ↓ InputManager.mLateInitContext
│                   ~~~~~~~~~~~~~~~~
├─ android.app.ContextImpl instance
│    Leaking: YES (ContextImpl.mOuterContext is an instance of androidx.fragment.app.ActivityLeakActivity with Activity.mDestroyed true)
│    Retaining 337.7 kB in 2497 objects
│    mOuterContext instance of androidx.fragment.app.ActivityLeakActivity with mDestroyed = true
│    ↓ ContextImpl.mOuterContext
╰→ androidx.fragment.app.ActivityLeakActivity instance
     Leaking: YES (ObjectWatcher was watching this because androidx.fragment.app.ActivityLeakActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
     Retaining 318.1 kB in 2293 objects
     key = 90cc2df3-0fea-4de0-b489-4296552a8606
     watchDurationMillis = 5276
     retainedDurationMillis = 271
     mApplication instance of androidx.fragment.app.LeakCanaryApp
     mBase instance of android.app.ContextImpl

We should add InputManager.mLateInitContext as a known leak pattern if this doesn't get fixed in the preview that ships.