Fixed
Status Update
No update yet.
Comments
ma...@google.com
as...@google.com
This is a product feature issue; not a developer issue. Our Android Support team will be in contact with you shortly.
In the meantime, here are helpful resources:
Android Help Center (https://support.google.com/android/?hl=en#topic=7313011 )
Pixel Help Center (https://support.google.com/pixelphone/?hl=en#topic=7078250 )
In the meantime, here are helpful resources:
Android Help Center (
Pixel Help Center (
br...@monzo.com
I have this problem as well.
I suggest Google open a fullscreen game for extended hours with keep switching between apps and the game and tapping the notifications.
While this bug does not really cause any functional problem, it impacts the user experience (esp the gaming experience) seriously.
I suggest Google open a fullscreen game for extended hours with keep switching between apps and the game and tapping the notifications.
While this bug does not really cause any functional problem, it impacts the user experience (esp the gaming experience) seriously.
as...@google.com
Same problem here. Status bar is overlaying at the top and home button at the bottom
ap...@google.com
Experiencing this after updating to Android 11 in Pixel 2 XL.
br...@monzo.com
This also happens on the Pixel 4a.
Description
Jetpack Compose version: I've tested on 1.3.0-alpha01 and 1.2.0-beta03
Jetpack Compose component(s) used: LazyColumn
Android Studio Build: 221.3427.89.2211.8689873
Kotlin version: 1.7.10
Steps to Reproduce or Code Sample to Reproduce:
Context:
We have a rather large (10k+ items) LazyColumn where scrolling (eventually) leads to the application grinding to a halt, constantly trying to free memory. It can't, we just keep getting lots of these:
Background concurrent copying GC freed 51964(1414KB) AllocSpace objects, 6(120KB) LOS objects, 0% free, 190MB/192MB, paused 101us total 1.483sI took at heap dump at this point and basically all of the heap is used up by instances of
SnapshotMutableStateImpl$StateStateRecord.Replace LazyColumn with a RecyclerView (with each item being a ComposeView) and the memory leak is gone. App performance is night and day better.
I've been trying for hours to reproduce this in a trivial sample project and haven't had any luck yet. Raising this anyway just in case you have any ideas about what might be causing it. Obviously this makes LazyColumn completely unusable for us, so we'll stick to RecyclerView for now!