android studio 3.0.1 taking forever to fetch results of memory allocation in android profiler

Question

I'm trying to profile my app's memory allocations but android studio is taking very long time to fetch results of allocation recording (in fact it's been 45 min and ITS STILL FETCHING !!!)

here's a screenshot

JUST LOOK AT THE TIME

you are only running one instance of Android Studio and you don't have Eclipse or ADB running at the same time in a separate window? — Sam, Dec 15 '17 at 16:41
Well I guess I've to brainstorm every part of my app until I find the bugs .. I hate old fashioned ways — Hesham Haikal, Dec 15 '17 at 16:51
The Android Profiler has performance issues. While [this issue](https://issuetracker.google.com/issues/68850784) may not be what you are experiencing, some of the suggestions in the comments might help. — CommonsWare, Dec 15 '17 at 17:16
It seems like this is still an issue with Profiler in 2019... — IgorGanapolsky, May 02 '19 at 16:52

score 1 · Answer 1 · answered Jan 09 '19 at 11:59

1

I had the same problem with Android Studio 3.2.1 and Samsung S5 on Android 6. I just used another device on Android 8 and allocations became visible. So, I guess, it depends on device or Android version.

answered Jan 09 '19 at 11:59

Aleksandr Urzhumtcev

328
1
3
14

How do we know which device to use? – IgorGanapolsky May 02 '19 at 16:53
Same problem here with AS 3.4 and a SGS5 too I'm using for testing. Weird! – Fran Marzoa May 17 '19 at 12:46

score 0 · Answer 2 · answered Dec 20 '21 at 16:28

0

My profiler was stuck on "fetching" because the debugger was also started and it paused my app because it reached a breakpoint

answered Dec 20 '21 at 16:28

Christian C

369
3
10

score -1 · Answer 3 · answered Jan 10 '18 at 20:26

One of the reasons that it could take a long time could be your method count been very huge, that by itself could be a memory issue if you got too many chained things in your code.

For example, you got class A sending some data to class B, let's say a username, and then class B sends it to class C et cetera... until it gets to class Z

You can break the chain by using a Singleton and make Z and any other class to pull the username data directly from the source.

To determinate if this indeed is your problem, try running the tool on a new test project with few lines of code.

android studio 3.0.1 taking forever to fetch results of memory allocation in android profiler

3 Answers3