Status Update
Comments
ti...@google.com <ti...@google.com> #2
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.
mo...@google.com <mo...@google.com> #3
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?
ky...@gmail.com <ky...@gmail.com> #4
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
mo...@google.com <mo...@google.com> #5
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.
mo...@google.com <mo...@google.com> #6
Ok so the good news is that the other issue is really fixed :) But this one not at all.
It seems 100% of the LazyInfo versions are kept in memory see new attachement.
I've sent you the full prof by mail as you probably can more easily find the root of the reference in the states to have some clues about what I need to do to reproduce.
ap...@google.com <ap...@google.com> #7
Ok so I speak too soon. There's an insane performance issue with 8506895 a simple lazycolumn with a few lazyrow now lags insanely.
Got lots of
Davey! duration=842ms; Flags=0, FrameTimelineVsyncId=30733, IntendedVsync=721976611111, Vsync=722518277756, InputEventId=0, HandleInputStart=722523309190, AnimationStart=722523309963, PerformTraversalsStart=722808544297, DrawStart=722808615383, FrameDeadline=722001544444, FrameInterval=722523205186, FrameStartTime=8333333, SyncQueued=722811912136, SyncStart=722812117702, IssueDrawCommandsStart=722812801825, SwapBuffers=722816362046, FrameCompleted=722819089423, DequeueBufferDuration=23560, QueueBufferDuration=2647257, GpuCompleted=722818621812, SwapBuffersCompleted=722819089423, DisplayPresentTime=0,
in logcat that I don't remember having seen before.
I guess that'll make a lot of repro to make :(
na...@google.com <na...@google.com> #8
According to profiler most is spent in compose:lazylist:prefetch:measure anything changed about that ?
Sorry for all the questions, but since huge time zone difference I try to gather the most info to be efficient tomorrow on both repro, as poor indie dev this is 100% unpaid time and I hate repro without any idea what to look after as it can take many hours.
Description
Jetpack Compose version: ToT
Related CL:https://android-review.googlesource.com/3202247
Steps to Reproduce or Code Sample to Reproduce:https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui/samples/src/main/java/androidx/compose/ui/samples/DialogSample.kt;l=33;drc=4d53400eca9f3ac90c3a3f6cffcbc5bf492ec536
Click outside and the dialog won't dismiss.