Apps-android-commons: Leaks needs to be solved before release

[neslihanturan]

Summary:

Here are leak reports needs to be solved before release (means this week)

Steps to reproduce:

Play with app, in general.

Add System logs:

This issue can be solved by several people. Please use comments efficiently to assign it yourselves by using letters (A/B/C/D/E/F).

Besides, this issue needs to be done in a week so help is appreciated :)

[yashshah7197]

I'll kick things off by taking up the the 'A' leak. I can try to fix all of them too if that's okay. 👍 @nicolas-raoul @neslihanturan

[neslihanturan]

Firstly you can start with 'A', since this issue is urgent and requires parallel working. If you are done with 'A' don't hesitate to get another one, after you wrote comment here @yashshah7197

[misaochan]

Thanks for volunteering to do "A", @yashshah7197 . :) If anyone else would like to take the others, please feel free to mention it here.

[yashshah7197]

@neslihanturan can you tell me how I could reproduce these leaks? LeakCanary doesn't seem to be detecting anything for me yet.

On a side note, sorry for the late updates. I'm down with a bit of fever and cough so can't really work on anything properly right now. 🙈

[neslihanturan]

@yashshah7197 just playing with app, I don't know either. I hope you get well soon.

[neslihanturan]

I am working on B and C

[neslihanturan]

@yashshah7197 this issues needs to be done today, will you be able to make it up? If not I will give a try.

[neslihanturan]

I am on D,E,F

[neslihanturan]

It seems like E and F is something we can ignore: https://medium.com/@amitshekhar/android-memory-leaks-inputmethodmanager-solved-a6f2fe1d1348

[misaochan]

Closing, we can create a new issue if there are further leaks. :)