Analyzer Tasks missing from profiler [117363840]

Fixed

Feature Request

Status Update

No update yet.

Description

gc...@gmail.com

created issue #1

Oct 7, 2018 09:08PM

Build: 3.2, AI-181.5540.7.32.5014246, 201809171917, AI-181.5540.7.32.5014246, JRE 1.8.0_152-release-1136-b06x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 2560x1440, 1920x1080Android Gradle Plugin: 3.2.0Gradle: 4.6NDK: from local.properties: 18.0.5002713; latest from SDK: 18.0.5002713; LLDB: LLDB 3.1 (revision: 3.1.4508709)CMake: from local.properties: (not specified); latest from SDK: 3.6.0-rc2; from PATH: (not found); IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

After profiling the memory of an app and saving the hprof file under the captures directory, opening the file via the Captures tab brings in the Heap Dump results.

However, the "Analyzer Tasks" are nowhere to be found so there is no way to find memory leaks.

Is this a bug or was the functionality removed?

Searching for the term "Analyzer Tasks" for AS does not bring any useful results.

Thanks

Comments

uc...@google.com <uc...@google.com> #2Oct 10, 2018 10:30PM

Assigned to sh...@google.com.

Looks similar to

issue 66148913

sh...@google.com <sh...@google.com> #3Oct 15, 2018 11:47PM

Thanks for the feedback. It is the limitation of our tool at this moment, but it's on our backlog to address in the future.

ci...@gmail.com <ci...@gmail.com> #4Mar 21, 2019 09:53PM

Anything on this?

sh...@google.com <sh...@google.com> #5Apr 8, 2019 11:13PM

Thanks for the ping. This hasn't been prioritized at this moment. We are investigating how best to improve the memory profiler including this request.

gc...@gmail.com <gc...@gmail.com> #6Apr 22, 2019 04:32PM

I don't understand... this IS how to best improve the profiler. It should be able to find leaks.

Can you at least provide a workaround?

This is the basis of a lot of ill behaved apps.

And for us that bother looking for leaks this is just not good enough.

Some help would be really appreciated.

Thanks

gc...@gmail.com <gc...@gmail.com> #7Apr 22, 2019 05:29PM

For people looking here...

I guess as mentioned on the linked issue in #2 a workaround is to:

*) save an hprof with latest AS (for example 3.4).
*) use AS 2.3.3 and open the hprof with that.

you can then find the root with meaningful attribution to the holding package/class.

FYI the root would be with depth 0 and it is easy to spot in AS 3.4 but the attribution to the owning package/class is not enough to find the culprit.
With 2.3.3 it is crystal clear!

sh...@google.com <sh...@google.com> Apr 29, 2019 04:25PM

Reassigned to sh...@google.com.

sh...@google.com <sh...@google.com> #8Apr 29, 2019 09:05PM

Thank you for the crystal clear feedback. Leak detection is surely on our to-do list.

gi...@gmail.com <gi...@gmail.com> #9Jul 5, 2019 05:05AM

Is there any ETA for adding the Analyzer task back into the profiler?

sh...@google.com <sh...@google.com> #10Jul 8, 2019 05:30PM

girishiitj@gmail.com: Thanks for the question. As a general rule, we don't comment on release schedule. But I can assure you that Analyzer Task has a high priority on our to do list.

sh...@google.com <sh...@google.com> #11Sep 18, 2019 09:06PM

Leak activities + fragments detection is now brought back since 3.6 canary 10 (

https://developer.android.com/studio/preview/index.html).

Please give it a go and let us know if you run into issues. Thanks!

sh...@google.com <sh...@google.com> #12Sep 20, 2019 05:51PM

Marked as fixed.

Marking this as fixed now. Please re-open if you run into issues!