leakcanary VS curtains

If your app exposes a LeakCanary Launcher activity, you will be able to quickly access it through the App Details bottom sheet.

Highly recommend you try out Leak Canary https://square.github.io/leakcanary/

First of all, grab the LeakCanary to check if you actually have a leak. Because just the memory increasing might be completely unrelated to your ViewPager.

It's strictly mContext otherwise it won't work as intended.

Knowing when root views are detached, e.g. to detect if they might be leaking (LeakCanary).

https://github.com/square/leakcanary + don't try to over optimise. In the end R8 / proguard / art runtime will do so many change between what you write and what actually is done that you may be loosing time doing something that the tools does for you.

LeakCanary

LeakCanary will help you find memory leaks in your code: https://square.github.io/leakcanary/

The library has great documentation, examples, samples, and FAQ. It is developed under Apache License, Version 2.0, and currently has a 1.2.1 version, so it is ready for production projects.

We leverage square/curtains to intercept touch events. We define TapTracker, a touch event interceptor. TapTracker stores the time of the last MotionEvent.ACTION_UP touch event. When the posted click listener triggers, we retrieve the time of the up event that triggered it by calling TapTracker.currentTap: