leakcanary VS gamedge

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/

To view the whole list of issues, take a look at the following link: https://github.com/mars885/gamedge/issues

You can take a look at my project called Gamedge. I try to keep it as up-to-date as possible and currently In the middle of converting it to Jetpack Compose.

7. Gamedge

PR migrating from Moshi to Kotlinx.Serialization.

If anyone want to take a look, here's a link to the GitHub.