Fixed
Status Update
No update yet.
Comments
cc...@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.
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
Version used: 1.1.0-beta01
Devices/Android versions reproduced on: any
When clicking on link to Stack Sampling Trace or Method Sampling Trace, it sometimes doesn't open proper trace file.
It happens when the profiling session was already opened in AS profiler.
This could be resolved with attaching datetime to the profiling file.
This would also improve the file not being overwritten with every benchmark run (+ we do the same thing with perfetto-trace).
Question is whether to do the same for benchmarkData.json?