Lazy Column -> List items dissapear once scrolled past and then don't reappear when scrolled back to [188566058]

Fixed

Bug

Status Update

No update yet.

Description

na...@vitruvian.me

created issue #1

May 19, 2021 07:10AM

Jetpack Compose release version: 1.0.0-beta07

Android Studio Build: Android Studio Arctic Fox | 2020.3.1 Canary 14

We have a set of non trivial list items which when scrolled past and then scrolled back to end up disappearing (see attached video). Issue only started happening when app was upgraded to compose beta07.

Additional info

Items are fed in with items(state.model.sessions.byDay[date].orEmpty().size)

Items expand when pressed and make use of animated visibility / animated size composables

I'm more than happy to share more code / try build a minimal recreation. If possible it would be good to get more direction on what areas could possibly cause this to help with the recreation as my current screen is non trivial. I tried just a basic lazy list with some text and that all worked as expected.

Thanks a tonne for all your work on this one!

dissapearing_list_items.mp4

7.6 MB

Download

Comments

ma...@google.com <ma...@google.com> May 19, 2021 11:15AM

Assigned to an...@google.com.

an...@google.com <an...@google.com> #2May 20, 2021 11:56AM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ed...@gmail.com <ed...@gmail.com> #3May 20, 2021 03:50PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

Message last modified on May 20, 2021 03:51PM

an...@google.com <an...@google.com> #4May 20, 2021 08:02PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

an...@google.com <an...@google.com> #5May 21, 2021 11:33AM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

ap...@google.com <ap...@google.com> #6May 24, 2021 05:55PM

On the contrary, there was no separate process before, when crashes started.

In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)

backtrace:
  #00  pc 000000000003c7c0  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003b960  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bb48  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bafc  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000036c98  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000032714  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000031cac  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000057438  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)

an...@google.com <an...@google.com> #7May 24, 2021 06:26PM

Marked as fixed.

FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model. https://developers.google.com/ml-kit/release-notes#august_11_2021

Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!

pz...@gmail.com <pz...@gmail.com> #8May 25, 2021 01:09AM

Thank you, I'll try it and check.

za...@gmail.com <za...@gmail.com> #9May 25, 2021 02:45AM

Hello. I have similar experience.

I'm using mlkit-language 16.1.1
I didnot meet this error until using AGP 4.2
I can get this error since using AGP 7.0
This error raised on Release build only(minimized by R8)
This error raised without obfuscation.