Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
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?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
ml...@google.com <ml...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
pr...@google.com <pr...@google.com> #4
-
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.
Description
Adding a
scrollBehavior
to aTopAppBar
causes theinnerPadding
property to recompose with the layout changes of the appbar. TheinnerPadding
propery is then passed into thecontent
lambda, which is read in composition and therefore recomposing thecontent
on every frame causing huge performance issue givenScaffold
is used usually per-screen.Deferring reading the
innerPadding
in the userland code doesn't fix the issue.Reproducible snippet:
This behavior also affects
material.Scaffold
, which can be fixed as well.