Lines Matching full:heap
71 <li> Overall heap status, useful for a heap bitmap display or
379 <h3>Heap Status</h3>
392 so the protocol allows the heap data to be sent in several chunks.
396 <p>All messages include a "heap ID" that can be used to differentiate
397 between multiple independent virtual heaps or perhaps a native heap. The
399 so all heap-specific information is tagged with a "heap ID".
402 <p>Request heap info.
415 <p>Heap Info. General information about the heap, suitable for a summary
420 For each heap:
422 u4 heap ID
425 u4 max heap size in bytes (-Xmx)
426 u4 current heap size in bytes
431 <p>[Do we need a "heap overhead" stat here, indicating how much goes to
435 <p>Request transmission of heap segment data.
447 <p>Request transmission of native heap segment data.
458 <p>This is a Heap Start message. It tells the server to discard any
459 existing notion of what the client's heap looks like, and prepare for
460 new information. HPST indicates a virtual heap dump and must be followed
462 heap dump and must be followed by zero or more NHSG messages and an NHEN.
466 u4 heap ID
470 <p>Heap End, indicating that all information about the heap has been sent.
475 u4 heap ID
479 <p>Heap segment data. Each chunk describes all or part of a contiguous
480 stretch of heap memory.
482 u4 heap ID
547 <p>Example: suppose a VM has a heap at 0x10000 that is 0x2000 bytes long
552 <p>The client must encode the entire heap, including all free space at
554 of memory in the heap. This refers to the current heap size, not the
555 maximum heap size.
562 information can be used to gain insights into heap layout.
570 <p>Native heap segment data. Each chunk describes all or part of a
571 contiguous stretch of native heap memory. The format is the same as
576 u4 heap ID
