Open markushi opened 2 weeks ago
I'm thinking about some workarounds that we can do, until it gets fixed (if it gets fixed in older Android versions) We can add another flag to guard "dangerous" profiles, and here is some idea for such detection:
Debug.startMethodTracingSampling
and Debug.stopMethodTracing
If you have any other workaround, feel free to add a comment with it The best would be create a custom profiler, but that's a big effort thing
Description
This is a meta issue to collect reported issues around Android Profiling and how we can improve profiling overall.
Refer to the individual issues to learn more about the status.