Does any have the issue that `LazyColumn` renders ...

# compose

[Tlaster]

Does any have the issue that LazyColumn renders blank item content after beta07? sample code and reproduce step in thread

[Tlaster]

MaterialTheme {
    Scaffold {
        LazyColumn {
            items(1000) {
                Text(text = "item $it")
            }
        }
    }
}

[Tlaster]

Scroll down for some distance and scroll up super fast, you will get something like this:

[Tlaster]

And in production if you checkout https://github.com/TwidereProject/TwidereX-Android with feature/compose-beta07 branch, you will got something like this easily if you scroll fast, notices the empty space between the divider. not sure if it's related

[Shakil Karim]

😨

[Shakil Karim]

I was about to update to Beta07.

[Andrey Kulikov]

@Tlaster for the first screenshot, could you try to set Modifier.fillMaxHeight() on LazyColumn? there was an old bug which looked similar and will be fixed for beta08

[Tlaster]

It still happens

[Andrey Kulikov]

I will try to checkout your project and reproduce, thanks

[Marco]

Has anyone resolved this?

[Andrey Kulikov]

I am still working on fixing the issue, but I don’t think there is a workaround for it. I suggest to stay on beta06 for now

[Andrey Kulikov]

for everyone affected: please follow this bug https://issuetracker.google.com/issues/188566058

[Marco]

Thanks for your answer!
In beta06, LazyColumn still suffers from UI stuttering though. Is there a workaround for a smooth list experience?

[Andrey Kulikov]

in beta07 the scrolling performance is improved a bit, but this bug is introduced. once I merge the fix I will share in the bug how to use the snapshot build with the fix, in case you would want to try it

[Andrey Kulikov]

FYI: shared a workaround in the bug

[joney]

It definitely helps. Though now only a single item at index 1 doesn't draw its content when scrolling up and down the first time. 🤔

2021_05_21_17_38_00_trim.mp4

[Andrey Kulikov]

interesting. can you show the code?

[Shakil Karim]

Is there any update to this issue?

[Andrey Kulikov]

In is now fixed in the main branch. see the bug for more details