Status Update
No update yet.
Comments
po...@google.com
May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.
pa...@google.com
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?
ap...@google.com
It happens even on screens that does not use the layoutInfo it just require many up / down flings.
LazyColumn(state = rememberLazyListState())
The only thing all screen have in common in that they have multiple item {} item{} block :(
Just in case the app is in open beta at
My main question before trying to do complex repro, is how much will it be relevant with all the recent changes in alpha 8 about Lazy stuff? And side question when
po...@google.com
I can't guarantee as I don't understand the issue yet, but I assume this issue is still not fixed, changes in alpha 8 were about different things.
Description
Given we plan the Box to be foundational component to build things with, we should probably see what we can do here.
Alert on dashboard:
CLs in build: aosp/1287601
Note: the shared model benchmark surfaces things like this more because it recomposes all the rectangles even when one changes (because they share reference to one model entry from the foreach loop)