Fixed
Status Update
Comments
je...@google.com <je...@google.com>
ha...@google.com <ha...@google.com>
[Deleted User] <[Deleted User]> #2
Also spent a good chunk of time debugging memory leaks in our apps and discovered the same thing. Upgraded all the way to `compose:1.3.0-alpha03` and `activity-compose:1.6.0-beta01` with the same leaks.
si...@google.com <si...@google.com> #3
This is a significant issue. Every app that integrates compose with an Activity will leak that Activity.
We automated a test to switch back and forth to an Activity for about 15 minutes. Attached screenshots of our results.
170 Leaks for referencing compose `setContentView` inside an Activity.
We automated a test to switch back and forth to an Activity for about 15 minutes. Attached screenshots of our results.
170 Leaks for referencing compose `setContentView` inside an Activity.
se...@google.com <se...@google.com>
ap...@google.com <ap...@google.com> #4
To workaround, we switched to Compose Navigation, which uses a single Activity. - https://developer.android.com/jetpack/compose/navigation
We ran the same automated test switch back and forth between screens for about 15 mins. Attached screenshots of our results.
0 Leaks.
We ran the same automated test switch back and forth between screens for about 15 mins. Attached screenshots of our results.
0 Leaks.
se...@google.com <se...@google.com>
na...@google.com <na...@google.com> #5
Are there any updates on this issue?
Our app relies on a lot of interop with ComposeView, and this leak has been causing issues and slowing down our integration with Compose.
Any help is much appreciated!
Description
Jetpack Compose release version: 1.0.1
Android Studio Build: 2021.1.1 Canary 9
Kotlin version: 1.5.21
This is a crash report received from a OnePlus Nord device running Android 11 (build
AC2001_14_210704
).The action appears to be:
Stack trace: