-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Leak] Toast$TN leaking in Android 11 #165
Comments
KaustubhPatange
added a commit
to KaustubhPatange/Moviesy
that referenced
this issue
Feb 21, 2021
I also encountered this problem |
Did you ever get this leak resolved? @KaustubhPatange |
Any updates on this Leak? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The leak is captured from LeakCanary.
This happens when the toast is in the queue (referenced) but the activity or containing fragment (in which it's about to show) goes out of existence. I've tested in on some devices & found out that Samsung devices are hotspots for this leak.
The fix, for now, is to set
allowQueue
to false fromToasty.Config
.The text was updated successfully, but these errors were encountered: