We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When enabling LeakCanary, we can detect a missing clear on the TabLayoutMediator when the FtueAuthSplashCarouselFragment is destroyed.
TabLayoutMediator
FtueAuthSplashCarouselFragment
No memory leak.
A memory leak is detected.
No response
No
Yes
The text was updated successfully, but these errors were encountered:
mnaturel
Successfully merging a pull request may close this issue.
Steps to reproduce
When enabling LeakCanary, we can detect a missing clear on the
TabLayoutMediator
when theFtueAuthSplashCarouselFragment
is destroyed.Outcome
What did you expect?
No memory leak.
What happened instead?
A memory leak is detected.
Your phone model
No response
Operating system version
No response
Application version and app store
No response
Homeserver
No response
Will you send logs?
No
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: