Fixed
Status Update
Comments
uc...@google.com <uc...@google.com>
sh...@google.com <sh...@google.com> #2
Sorry but It is a known inconvenience in AS 3.0 for now. As a workaround, you can:
1. Export the dump from Profiler via a toolbar button (see attached screenshot).
2. Then, re-open the file in Studio, which will bring you to the old hprof viewer where the analyzer tasks are available.
Going forward, we will have the leak detection workflow better integrated into the new profiler.
Hope that helps...
1. Export the dump from Profiler via a toolbar button (see attached screenshot).
2. Then, re-open the file in Studio, which will bring you to the old hprof viewer where the analyzer tasks are available.
Going forward, we will have the leak detection workflow better integrated into the new profiler.
Hope that helps...
pa...@outlook.com <pa...@outlook.com> #3
The workaround does not bring the old HPROF viewer, it keeps opening the new one. This is on Android Studio 3.2.1.
This is very inconvenient since it forces us to either a) use the AS 2x so we can use a proper analyzer tool that has these features or b) use a third-party tool that is not reliable (LeakCanary is currently plagued by false positives causing a bigger waste of time than actual debug help)
This is very inconvenient since it forces us to either a) use the AS 2x so we can use a proper analyzer tool that has these features or b) use a third-party tool that is not reliable (LeakCanary is currently plagued by false positives causing a bigger waste of time than actual debug help)
sh...@google.com <sh...@google.com> #4
Leak activities + fragments detection is now brought back since 3.6 canary 10 (https://developer.android.com/studio/preview/index.html ).
Closing this bug for now. Please give it a go and reopen this if you run into issues. Thanks!
Closing this bug for now. Please give it a go and reopen this if you run into issues. Thanks!
Description
The alternative seems to be to trawl through the list of classes finding all the Activities (a filter would help here), then where count is >1 click it to see if only one of them has a depth (I assume the others just haven't been GCed yet).
Analyzer task is much quicker :-)
"Find Duplicate Strings" is also missing, I'm not sure how useful that was.