Verified
Status Update
No update yet.
Comments
yb...@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?
cc...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
cc...@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
Version used: 1.0.0-alpha5
Devices/Android versions reproduced on: n/a
A PagedList has access to the DataSource that we supply to page against. Admittedly, in the current PagedList implementation, that is buried under some wrapper layers.
Some DataSource implementations may require us to clean them up when we are done with them (e.g., to avoid garbage collection issues). When we are done with a PagedList, in many cases we are done with the DataSource backing that PagedList. It stands to reason that we should be able to retrieve our DataSource from the PagedList in order to be able to clean it up (e.g., call some close() method).
Thanks for considering this!