views:

174

answers:

3

I need to check my application for memory leaks, i also need to see the memory allocation of my application. I downloaded and installed eclipse memory analyzer, and it looks like the first step is to open a heap dump. But what is a heap dump, how can i create a heap dump. And how exactly am i going to use this software, I did some googling but i couldn't find any useful information thanks

+3  A: 

When you debug your app, open DDMS in Eclipse. On the toolbar there is a heap dump button that you can use to generate a heap dump to view in Eclipse memory analyzer. This is only supported I think with the 1.6+ or 2.0+ SDK.

BrennaSoft
Ok so i clicked dump, and it opened a new window named android123123123 with lots of weird characters in it.What do i do with this page?Where is the file?Thanks again
aryaxt
I figured it out myself.File ==> Save As, then opened the file in memory analyzer
aryaxt
A somewhat longer explanation: http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/heap-profiling.html;hb=HEAD
fadden
A: 

The heap dump of the dalvik VM needs to be converted to regular hprof format using the hprof-conv.exe converter tool in the tools directory of the Android SDK. You can open this hprof with Eclipse MAT or other tools are: YourKit http://www.yourkit.com/ and JProbe http://www.quest.com/jprobe/

Beside DDMS you can also create the hprof from you app/code (only newer SDKs) via Debug.dumpHprofData(...)

Note that in DDMS you can see the heap that your app is using. It doesn't show the native heap that external resources such as bitmaps are allocating. Nevertheless, these resources also need to be taken into account when checking for memory leaks. When both native and app heap adds up to 16MB / resp. 24MB you will get an OOM error.

You can see the native heap that's been used (i.e. by bitmaps in your app) via Debug.getNativHeapAllocatedSize().

Mathias Lin
I'm on mac there is no such a thning as exe, and i didn't have to do anything with the file, I simply saved it as it was from eclipse, and i opened it with memory analyzer, with no problem
aryaxt