Memory leaks when setting up Recycler/Adapter

[anhanh11001]

Describe the bug
In most fragment, setting up RecyclerView and Adapter leads to memory leaks reported by Leak Canary

Screenshots

Additional context
#1705 related issue

Would you like to work on the issue?
Yes

[iamareebjamal]

Reopening because there might be other reasons for memory leaks. Please check @anhanh11001

[anhanh11001]

@liveHarshit can you also take a look at this issue as well, I'm not sure for now

[liveHarshit]

@liveHarshit can you also take a look at this issue as well, I'm not sure for now

Sure 👍
This issue needs to divide into different parts. There are multiple memory leaks. We can list them manually and solve them.

[liveHarshit]

@anhanh11001 @iamareebjamal What if we use data bindings for fragments instead of using lateinit rootView, I think it is causing for memory leaks.

[iamareebjamal]

It's not. The listeners are causing the memory leak. If you use the binding. binding and hence, the root view will get leaked

[liveHarshit]

Okay and leaking always starts with message Fragment#mFragmentManager is not null in case of recycling adapters, I don't understand what it's mean?