IssueTracker

Hi, thanks for report!

Could you attach a bit more information about the heap at this point (e.g. a heap dump) if the leak is not reproducible in trivial project?

Attached!

I looked into the heap dump, seems like we are not disposing certain snapshots. Current snapshot id seems to be around 42k, but we have 108, 116 and 14123 in invalid SnapshotIdSet for current global snapshot. It is hard to figure out what caused it without repro though, as those snapshots seem to be already collected by GC.

I managed to repro it after a bunch of debugging. The bad news is that it's caused when using Coil within a LazyColumn, so that library is doing something that's causing you to leak snapshots... somehow.

Repro:

1. Add implementation io.coil-kt:coil-compose:2.1.0 to build.gradle
2. Add the following composable:

@Composable fun Leak() {
    val lazyListState = rememberLazyListState()
    val items by remember { mutableStateOf(List(10000) { it }) }

    LazyColumn(state = lazyListState) {
        items(items) {
            Box(Modifier.fillMaxWidth()) {
                AsyncImage(
                    model = "https://i.picsum.photos/id/104/200/200.jpg?hmac=3XxEVXVjwoI45-6sum_iMwNZ52GT-SJacVWr4fh4hqI",
                    contentDescription = null
                )
            }
        }
    }
}

3. Scroll
4. Memory 📈

Thanks for the quick turnaround!

The following release(s) address this bug:

• androidx.compose.runtime:runtime:1.3.0

Where is this emulator build number

Click the "..." (three dots on the emulator panel), then "Help", then "About".

As the emulator update, where is the place to download the image zip files.

#comment2 has a link, but since you mentioned Ubuntu, you want to download sdk-repo-linux-emulator-10591065.zip.

Thanks for the info.

Yes, my current emulator is 32.1.12-9751036, after updated the emulator version, the mic settings persistent saving is working now.

Also the mic is also working for API-33 when enabled.

By the way, any reason why I did not get a notification to update the emulator. I believe it was so in the past. Did I accidentally disabled the auto update option.

Thanks for the help.

By the way, any reason why I did not get a notification to update the emulator.

I am not sure, as the SDK Manager is a different component. Yes, 32.x.x is somewhat old.