material-components-android VS leakcanary

It works with both. Components for the view system are available on Github.

By going to the Github doc of the material components lib, you can change branches and easily check when the design was updated. The latest release with the old design is 1.4 (see this doc).

TargetSDK is 33

[Tokens/Color] Added U color resources for contrast mode support.

You mean this one? https://github.com/material-components/material-components-android/blob/master/docs/components/Search.md

I'm not a dev, but I'm curious about this, cause I thought Material Components was made years ago as a library for devs to dynamically use said material components, so they would have an easier time updating their apps when the guidelines changed. Did I interpret it wrong?

Material Components has ToggleButton which does exactly what you want

It's probably worth filing an issue about it https://github.com/material-components/material-components-android/issues

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/