Fixed
Status Update
No update yet.
Comments
lp...@google.com
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?
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com
-
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
Currently we have canScrollForward / canScrollBackward state in lazy* APIs - this would be generically useful for all scrollable components and would allow developers to more easily implement features such as scroll to top / bottom buttons, indicators to show that there is more scrollable content in a certain direction and buttons (such as arrows in a scroll bar) to manually scroll by a fixed delta.
It would also allow us to make other performance / optimization improvements that would be worth investigating:
Only dispatch scroll deltas if we can scroll in that direction (i.e we are not at the end of the scrollable component)
Not dispatch scroll deltas or overscroll if we can scroll in neither direction (e.g the scrollable bounds are smaller than the viewport)