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

Asked 15/12, 2017 at 16:37 Answered 20/12, 2021 at 16:28

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

Marshy answered 15/12, 2017 at 16:37 Comment(8)

Try restarting it – Blest 15/12, 2017 at 16:38

I did .. like 3 times – Marshy 15/12, 2017 at 16:39

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? – Escalate 15/12, 2017 at 16:41

Yup , only android studio – Marshy 15/12, 2017 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 – Marshy 15/12, 2017 at 16:51

The Android Profiler has performance issues. While this issue may not be what you are experiencing, some of the suggestions in the comments might help. – Ogawa 15/12, 2017 at 17:16

It seems like this is still an issue with Profiler in 2019... – Joappa 2/5, 2019 at 16:52

2024 here. Nothing changed, it still freezes every time (right now -- trying to fetch a heap dump). That's what I call "stable software". – Exigent 24/8 at 20:17

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.

Deakin answered 9/1, 2019 at 11:59 Comment(2)

How do we know which device to use? – Joappa 2/5, 2019 at 16:53

Same problem here with AS 3.4 and a SGS5 too I'm using for testing. Weird! – Oliveolivegreen 17/5, 2019 at 12:46

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

Halette answered 20/12, 2021 at 16:28 Comment(0)

-1

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.

Hillari answered 10/1, 2018 at 20:26 Comment(0)

Recommended topics

Hot tags