AnalogWatchFace VS leakcanary

The watch face is and will always be free and open-source. So if you are a developer feel free to contribute. All contributions are welcome (refactoring, adding tests, adding new features, adding new watch face designs, fixing typos ...), but if you are planning a big change it would be great if you could contact me beforehand. Here is the repo: https://github.com/VladimirWrites/AnalogWatchFace

Finally, the app is and will always be open-sourced and free. https://github.com/VladimirWrites/AnalogWatchFace Feel free to contribute, or to take the whole codebase and create your watch face.

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/