Status Update
No update yet.
Comments
cc...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
yi...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
cc...@google.com
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.
na...@google.com
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.
Description
Component used: Studio Dolphin Beta 05
Versions used: Macrobenchmark 1.1.0
Devices/Android versions reproduced on: Pixel 3 API 31, SM-F926B API 31
System trace allows to investigate janky frames in studio/perfetto on SDK >= 31. When a system trace is recorded manually (from studio) on a profileable app, it gives information on various phases - App, GPU, Composition (see screenshot).
When the system trace is recorded with the Macrobenchmark, it still gives the janky frames, but the phases are unavailable (see screenshot).
Can we query for this kind of data as well?