Status Update
No update yet.
Comments
lh...@gmail.com
This functionality was released in benchmark 1.2.0-alpha06:
You'll need to use an Android 13 (API 33) emulator, and androidx.benchmark:benchmark-macro-junit4:1.2.0-alpha06, which removes the requirement for root, and thus works on Play emulator images.
lh...@gmail.com
My system version is android 9
wd...@google.com
ad...@google.com
ad...@google.com
From the idea.log file, it implies to be an issue with device. Can you see if restarting the device help. Also, Can you please provide Logcat to help us look into this issue.
lh...@gmail.com
Thanks for the reply.
The device runtime log is in the attachment.
I have the source code for the device system and can compile it to generate an image, so if it can be fixed, please tell the method.
BTW: Consider displaying the error on the device in AS, at least to let the user know it's a device error.
lh...@gmail.com
I install the system apps that need to be debugged, with system signatures.
I just installed the normal app to do the same and surprisingly it works fine.
I need system permissions ah, some resources to be able to call.
lh...@gmail.com
I figured out the smallest change that was causing the problem.
After adding debug to signingConfigs and using platform.jks (system signing), the function "Record Java/Kotlin allocations" doesn't work.
lh...@gmail.com
I found a way to fix the problem for now by removing the signature, "setenforce 0".
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
This error "There was an error load ing this feature. Try restarting the profiler to fix it." appears when using the profiler, and cannot Record Java / Kotlin allocations, and keeps getting stuck at Setting up allocation tracking.
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A. Profiler -> +(Devices and processes appear to be very slow) -> Device & Processes
3B. Record Java / Kotlin allocations & Record
3C. Always on "Setting up allocation tracking"
In addition to logs, please attach a screenshot or recording that illustrates the problem.
For more information on how to get your bug routed quickly, see
Build: AI-231.9392.1.2311.11047128, 202311031549
AI-231.9392.1.2311.11047128, JRE 17.0.7+0-17.0.7b1000.6-10550314x64 JetBrains s.r.o., OS Mac OS X(aarch64) v14.1.1, screens 2880.0x1800.0, 2560.0x1440.0; Retina
AS: Hedgehog | 2023.1.1 RC 3
Kotlin plugin: 231-1.9.10-release-459-AS9392.1.2311.11047128
Android Gradle Plugin: 3.6.3
Gradle: 5.6.4
Gradle JDK: Azul Zulu version 11.0.19
NDK: from module: , from module: , from local.properties: 20.0.5594570, latest from SDK: 25.2.9519653
CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.27.3
```