From 2102ac1eed2fd065a2cd29a3f3729f124657e223 Mon Sep 17 00:00:00 2001 From: Ricardo Cervera Date: Tue, 21 Oct 2014 10:12:08 -0700 Subject: [PATCH] docs: Fix hprof-conv location in docs. https://code.google.com/p/android/issues/detail?id=76691 Change-Id: I8550731c1defe867d26d5ab4568c4935c89e37d6 --- docs/html/tools/debugging/debugging-memory.jd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd index fccb67ec7a609..ae67b3c16df79 100644 --- a/docs/html/tools/debugging/debugging-memory.jd +++ b/docs/html/tools/debugging/debugging-memory.jd @@ -243,7 +243,7 @@ here, as some details of the output differ across platform versions.

Other mmap 107 0 8 8 324 68 Unknown 6994(4) 0 252 6992(4) 0 0 TOTAL 24358(1) 4188 9724 17972(2)16388 4260(2)16968 16595 336 - + Objects Views: 426 ViewRootImpl: 3(8) AppContexts: 6(7) Activities: 2(7) @@ -251,7 +251,7 @@ here, as some details of the output differ across platform versions.

Local Binders: 64 Proxy Binders: 34 Death Recipients: 0 OpenSSL Sockets: 1 - + SQL MEMORY_USED: 1739 PAGECACHE_OVERFLOW: 1164 MALLOC_SIZE: 62 @@ -374,7 +374,7 @@ all app processes, they don’t matter very much to your own heap analysis.

To analyze your heap dump, you can use a standard tool like jhat or the Eclipse Memory Analyzer Tool (MAT). However, first you'll need to convert the HPROF file from Android's format to the J2SE HPROF format. You can do -this using the hprof-conv tool provided in the <sdk>/tools/ +this using the hprof-conv tool provided in the <sdk>/platform-tools/ directory. Simply run the hprof-conv command with two arguments: the original HPROF file and the location to write the converted HPROF file. For example: