You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I integrated this app in my library and Leakcanary detects a memory leak of linear layout if the app is minimized when welcome screens are open and then resumed back again. It seems the issue is the line:
welcomeScreen = new WelcomeHelper(this, MyWelcomeActivity.class);
We are passing an instance of this to welcome activity but when the base activity lifecycle actions happen, WelcomeHelper still holds the instance to the base activity leading to GC not able to run on it and thus a memory leak.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I integrated this app in my library and Leakcanary detects a memory leak of linear layout if the app is minimized when welcome screens are open and then resumed back again. It seems the issue is the line:
We are passing an instance of
this
to welcome activity but when the base activity lifecycle actions happen,WelcomeHelper
still holds the instance to the base activity leading to GC not able to run on it and thus a memory leak.Please help @stephentuso
The text was updated successfully, but these errors were encountered: