Cross Reference: /dalvik/docs/heap-profiling.html

Lines Matching full:dump
10 The Dalvik virtual machine can produce a complete dump of the contents
22 The first step is to cause the VM to dump its status, and then pull the hprof
34 access, because of the way the dump is initiated and where the output
63 The signal causes a GC, followed by the heap dump (to be completely
65 dump reflect the post-GC state).  This can take a couple of seconds,
71 # ls /data/misc/heap-dump*
81 <code>/data/misc/heap-dump-BLAH-BLAH.hprof</code> and
87 $ adb pull /data/misc/heap-dump-BLAH-BLAH.hprof tail.hprof
88 $ adb pull /data/misc/heap-dump-BLAH-BLAH.hprof-head head.hprof
89 $ adb shell rm /data/misc/heap-dump-BLAH-BLAH.hprof /data/misc/heap-dump-BLAH-BLAH.hprof-head
96 $ cat head.hprof tail.hprof &gt; dump.hprof
101 You now have the hprof dump in <code>dump.hprof</code>.
109 a program to write the dump at will to a specific file.  If you're not
116 completion you will see a log message that says "hprof: heap dump completed".
121 I/dalvikvm(  289): SIGUSR1 forcing GC and HPROF dump
122 I/dalvikvm(  289): hprof: dumping VM heap to "/data/misc/heap-dump-tm1240861355-pid289.hprof-hptemp".
123 I/dalvikvm(  289): hprof: dumping heap strings to "/data/misc/heap-dump-tm1240861355-pid289.hprof".
124 I/dalvikvm(  289): hprof: heap dump completed, temp file removed
130 Send the <code>SIGUSR1</code> or use the API call to initiate a dump.
131 Use <code>adb pull &lt;dump-file&gt;</code> and <code>adb shell rm
132 &lt;dump-file&gt;</code> to retrieve the file and remove it from the
160 In 2.0, features were added that allow DDMS to request a heap dump on
162 and click the "dump HPROF file" button in the top left.  This always
170 DDMS heap dump requests are now streamed directly out of the VM, removing
OpenGrok
