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.

Sign up for GitHub

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

Jump to bottom

Memomry leak caused by ComposeView detected by LeakCanary #94

Open

racka98 opened this issue Nov 3, 2022 · 0 comments

Labels

bug P1

Collaborator

racka98 commented Nov 3, 2022

Describe the bug
After the ComposeView in AppScreenTimeOverlayUI is detached from the Window it stays in memory and leaks.

All details match this issue that hasn't been fixed yet: https://issuetracker.google.com/issues/240975572

To Reproduce
Steps to reproduce the behavior:

Set a screen time limit for an App
Open the app so the block overlay ui shows up
Exit the Overlay using the Exit Button or Home button
Leak canary will be observing the ComposeView instance and report that it's leaking

Expected behavior
ComposeView for AppScreenTimeOverlayUI should be destroyed and should not stay in memory

Screenshots
Will attach stack trace later

Device:

Model: Pixel 4a 5G
OS: Android
Version: 13 (API 33)
App version: 1.0.0-alpha07

Additional context
None at the moment

racka98 added bug P1 labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment