Crash in Jetchat on rotation: "IllegalStateException: Reading a state that was created after the snapshot..." [193006595]

Fixed

Bug

Status Update

No update yet.

Description

ja...@google.com

created issue #1

Jul 7, 2021 10:57AM

java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied

Jetpack Compose release version: 1.0.0-rc01
androidGradlePlugin "com.android.tools.build:gradle:7.1.0-alpha02" and "com.android.tools.build:gradle:7.0.0-beta04"
Accompanist version = "0.13.0"
Android Studio Build: Bumblebee canary 2 and AF beta3
Jetchat version v1.0.0-rc01 ->

https://github.com/android/compose-samples/releases/tag/v1.0.0-rc01
Emulator used: Pixel 2 API 30

Steps to Reproduce:
1. Open Jetchat
2. Open Profile screen (through drawer or clicking on avatar)
3. Rotate device

This is a regression.

Crash:

java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied
at androidx.compose.runtime.snapshots.SnapshotKt.readError(Snapshot.kt:1530)
at androidx.compose.runtime.snapshots.SnapshotKt.readable(Snapshot.kt:1526)
at androidx.compose.runtime.snapshots.SnapshotKt.readable(Snapshot.kt:1517)
at androidx.compose.runtime.SnapshotMutableStateImpl.getValue(SnapshotState.kt:143)
at com.google.accompanist.insets.InsetsPaddingValues.getAdditionalStart-D9Ej5fM(Padding.kt:345)
at com.google.accompanist.insets.InsetsPaddingValues.calculateLeftPadding-u2uoSUM(Padding.kt:299)
at androidx.compose.foundation.layout.PaddingValuesModifier$measure$2.invoke(Padding.kt:423)
at androidx.compose.foundation.layout.PaddingValuesModifier$measure$2.invoke(Padding.kt:421)
at androidx.compose.ui.layout.MeasureScope$layout$1.placeChildren(MeasureScope.kt:68)
at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.placeAt-f8xVGno(DelegatingLayoutNodeWrapper.kt:111)
at androidx.compose.ui.layout.Placeable.access$placeAt-f8xVGno(Placeable.kt:31)
at androidx.compose.ui.layout.Placeable$PlacementScope.placeRelative(Placeable.kt:359)
at androidx.compose.ui.layout.Placeable$PlacementScope.placeRelative$default(Placeable.kt:179)
at androidx.compose.foundation.layout.PaddingModifier$measure$1.invoke(Padding.kt:370)
at androidx.compose.foundation.layout.PaddingModifier$measure$1.invoke(Padding.kt:368)

(full trace attached)

crashjetchat.txt

34 KB

View

Download

Comments

ja...@google.com <ja...@google.com> #2Jul 7, 2021 10:58AM

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?

ja...@google.com <ja...@google.com> #3Jul 7, 2021 11:02AM

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

ja...@google.com <ja...@google.com> #4Jul 7, 2021 11:05AM

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.

ja...@google.com <ja...@google.com> #5Jul 7, 2021 11:08AM

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.

an...@google.com <an...@google.com> Jul 7, 2021 11:30AM

Assigned to ch...@google.com.

ch...@google.com <ch...@google.com> #6Jul 7, 2021 10:07PM

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)

ap...@google.com <ap...@google.com> #7Jul 8, 2021 06:47PM

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!