Fixed
Status Update
No update yet.
Comments
uc...@google.com
Thank you for suggesting this enhancement. We value the feedback from our community and hope to review your suggestion in an upcoming sprint.
da...@google.com
Billy, this bug was originally reported in 3.0.1. Essentially: if the profiler window isn't open, we shouldn't copy perfd etc. files to the device. I think this is our current behavior, can you confirm?
mmurphy, if you're still there, could you also confirm if you see this happening with latest? Thanks!
mmurphy, if you're still there, could you also confirm if you see this happening with latest? Thanks!
sh...@google.com
This was addressed in 3.2.
If the Profiler tool window is not visible, running an app will not trigger the file copy into the app's data folder.
Please re-open this bug if the issue is still happening.
If the Profiler tool window is not visible, running an app will not trigger the file copy into the app's data folder.
Please re-open this bug if the issue is still happening.
Description
In a nutshell, on Android Studio 3.0.1, having ever had the Android Profiler tool window open means that libperfa_arm64.so, perfa.jar, and perfd are added to the /data/data/.../ directory for the app. I assume that the code in the JAR and SO are injected into the app's process by some means.
While there is an "Enable advanced profiling" checkbox, that only controls API Level 25 and older devices. API Level 26+ devices always get this stuff copied into the app directory, if the Profiler tool window was ever open in this invocation of the IDE.
Please provide a checkbox or something to disable this functionality. Alternatively, only enable this functionality if the Profiler tool window is open and visible at the time of running the app, not just having existed at some point in the IDE process' past. If that means that the Android Profiler does not work in this disabled state, put a warning message in the Profiler window, akin to the ones shown for "no device" and "no debuggable process".
IOW, do not add stuff to our apps or their /data directory, and do not inject code into running app processes, *without the express consent of the developer*.
Thanks!