Status Update
Comments
l....@gmail.com <l....@gmail.com> #2 Restricted
ko...@google.com <ko...@google.com>
sh...@google.com <sh...@google.com> #3
Thanks for reporting the issue. The log shows you were using a userdebug phone. Can you try a user build phone? User build phones are our target use scenario and best tested.
The screen recording shows three attempts of CPU recordings. The first two failed, while the third one succeeded. Can you reproduce the errors in the first two attempts consistently? Can you try another phone of user build? That could rule out the factor of the phone.
I confirm the message "There was an error loading this feature. Try restarting the profiler to fix it.
" is a bug, but it shouldn't impact CPU recordings.
Another suggestion is to use "Profile with low overhead" to launch the app in Android Studio Flamingo. It would give you the more accurate results in CPU recoridngs.
Description
STEPS TO REPRODUCE:
1. Run app with profiling
2. Record a callstack sample
3. AS says it can't read it
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build:
Version of Gradle Plugin: 7.4.2
Version of Gradle: 8.0.2
Version of Java: 19 on host (but 17 in AS)
OS: macos