Assigned
Status Update
Comments
an...@google.com <an...@google.com>
ap...@google.com <ap...@google.com> #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.
lo...@gmail.com <lo...@gmail.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.
ch...@google.com <ch...@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.
ns...@gmail.com <ns...@gmail.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!
ch...@google.com <ch...@google.com> #6
This is a huge bug and the memory keeps growing
na...@google.com <na...@google.com> #7
Do we know if this is fixed in Compose 1.3.0
or 1.3.1
?
Has anyone (or OP) tried repro-ing with those versions yet?
Thanks
ns...@gmail.com <ns...@gmail.com> #8
FWIW, just tried to repro the leaks with Compose + Compose Compiler 1.3.1
and the leaks seem to have stopped.
Would love confirmation about this being fixed in 1.3.1
just to be sure.
Description
After upgrading to compose 1.3.0-beta03, my app started crashing. After investigating the issue, I was able to reproduce it in a minimal example which you can find here:https://github.com/ln-12/compose-1.3.0-crash-example
For me, it is only happening with the
AlertDialog
component.Steps to Reproduce or Code Sample to Reproduce:
produceState
to create a simple state which changesStack trace (if applicable):