Edit File by line

[0] Fix | Delete

[1] Fix | Delete

Redistribution and use in source and binary forms, with or without

[2] Fix | Delete

modification, are permitted provided that the following conditions

[3] Fix | Delete

are met:

[4] Fix | Delete

[5] Fix | Delete

- Redistributions of source code must retain the above copyright

[6] Fix | Delete

notice, this list of conditions and the following disclaimer.

[7] Fix | Delete

[8] Fix | Delete

- Redistributions in binary form must reproduce the above copyright

[9] Fix | Delete

notice, this list of conditions and the following disclaimer in the

[10] Fix | Delete

documentation and/or other materials provided with the distribution.

[11] Fix | Delete

[12] Fix | Delete

- Neither the name of Oracle nor the names of its

[13] Fix | Delete

contributors may be used to endorse or promote products derived

[14] Fix | Delete

from this software without specific prior written permission.

[15] Fix | Delete

[16] Fix | Delete

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS

[17] Fix | Delete

IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,

[18] Fix | Delete

THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

[19] Fix | Delete

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR

[20] Fix | Delete

CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

[21] Fix | Delete

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

[22] Fix | Delete

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

[23] Fix | Delete

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

[24] Fix | Delete

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

[25] Fix | Delete

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

[26] Fix | Delete

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

[27] Fix | Delete

[28] Fix | Delete

[29] Fix | Delete

Header for -agentlib:hprof (or -Xrunhprof) ASCII Output (JDK 5.0 JVMTI based)

[30] Fix | Delete

[31] Fix | Delete

WARNING! This file format is under development, and is subject to

[32] Fix | Delete

change without notice.

[33] Fix | Delete

[34] Fix | Delete

This file contains the following types of records:

[35] Fix | Delete

[36] Fix | Delete

THREAD START

[37] Fix | Delete

THREAD END mark the lifetime of Java threads

[38] Fix | Delete

[39] Fix | Delete

TRACE represents a Java stack trace. Each trace consists

[40] Fix | Delete

of a series of stack frames. Other records refer to

[41] Fix | Delete

TRACEs to identify (1) where object allocations have

[42] Fix | Delete

taken place, (2) the frames in which GC roots were

[43] Fix | Delete

found, and (3) frequently executed methods.

[44] Fix | Delete

[45] Fix | Delete

HEAP DUMP is a complete snapshot of all live objects in the Java

[46] Fix | Delete

heap. Following distinctions are made:

[47] Fix | Delete

[48] Fix | Delete

ROOT root set as determined by GC

[49] Fix | Delete

CLS classes

[50] Fix | Delete

OBJ instances

[51] Fix | Delete

ARR arrays

[52] Fix | Delete

[53] Fix | Delete

SITES is a sorted list of allocation sites. This identifies

[54] Fix | Delete

the most heavily allocated object types, and the TRACE

[55] Fix | Delete

at which those allocations occurred.

[56] Fix | Delete

[57] Fix | Delete

CPU SAMPLES is a statistical profile of program execution. The VM

[58] Fix | Delete

periodically samples all running threads, and assigns

[59] Fix | Delete

a quantum to active TRACEs in those threads. Entries

[60] Fix | Delete

in this record are TRACEs ranked by the percentage of

[61] Fix | Delete

total quanta they consumed; top-ranked TRACEs are

[62] Fix | Delete

typically hot spots in the program.

[63] Fix | Delete

[64] Fix | Delete

CPU TIME is a profile of program execution obtained by measuring

[65] Fix | Delete

the time spent in individual methods (excluding the time

[66] Fix | Delete

spent in callees), as well as by counting the number of

[67] Fix | Delete

times each method is called. Entries in this record are

[68] Fix | Delete

TRACEs ranked by the percentage of total CPU time. The

[69] Fix | Delete

"count" field indicates the number of times each TRACE

[70] Fix | Delete

is invoked.

[71] Fix | Delete

[72] Fix | Delete

MONITOR TIME is a profile of monitor contention obtained by measuring

[73] Fix | Delete

the time spent by a thread waiting to enter a monitor.

[74] Fix | Delete

Entries in this record are TRACEs ranked by the percentage

[75] Fix | Delete

of total monitor contention time and a brief description

[76] Fix | Delete

of the monitor. The "count" field indicates the number of

[77] Fix | Delete

times the monitor was contended at that TRACE.

[78] Fix | Delete

[79] Fix | Delete

MONITOR DUMP is a complete snapshot of all the monitors and threads in

[80] Fix | Delete

the System.

[81] Fix | Delete

[82] Fix | Delete

HEAP DUMP, SITES, CPU SAMPLES|TIME and MONITOR DUMP|TIME records are generated

[83] Fix | Delete

at program exit. They can also be obtained during program execution by typing

[84] Fix | Delete

Ctrl-\ (on Solaris) or by typing Ctrl-Break (on Win32).

[85] Fix | Delete

[86] Fix | Delete