jmap(1) [mojave man page]
jmap(1) General Commands Manual jmap(1) NAME
jmap - memory map SYNOPSIS
jmap [ option ] pid jmap [ option ] executable core jmap [ option ] [ server-id@ ] remote-hostname-or-IP DESCRIPTION
jmap prints shared object memory maps or heap memory details of a given process or core file or remote debug server. NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK. jmap is not currently available on Windows platforms or on the Linux Itanium platform. PARAMETERS
option Options are mutually exclusive. Option, if used, shouldfollow immediately after the command name. pid process id for which the memory map is to be printed. The process must be a Java process. To get a list of Java processes running on a machine, jps may be used. executable Java executable from which the core dump was produced. core core file for which the memory map is to be printed. remote-hostname-or-IP remote debug server's (see jsadebugd) hostname or IP address. server-id optional unique id, if multiple debug servers are running on the same remote host. OPTIONS
<no option> When no option is used jmap prints shared object mappings. For each shared object loaded in the target VM, start address, the size of the mapping, and the full path of the shared object file are printed. This is similar to the Solaris pmap util- ity. -heap Prints a heap summary. GC algorithm used, heap configuration and generation wise heap usage are printed. -histo Prints a histogram of the heap. For each Java class, number of objects, memory size in bytes, and fully qualified class names are printed. VM internal class names are printed with '*' prefix. -permstat Prints class loader wise statistics of permanent generation of Java heap. For each class loader, its name, liveness, address, parent class loader, and the number and size of classes it has loaded are printed. -h Prints a help message. -help Prints a help message. SEE ALSO
pmap(1) jps(1) jsadebugd(1) 13 June 2004 jmap(1)
Check Out this Related Man Page
heap(1) BSD General Commands Manual heap(1) NAME
heap -- List all the malloc-allocated buffers in the process's heap SYNOPSIS
heap [-s | -sortBySize] [-z | -zones] [-guessNonObjects] [-sumObjectFields] [-showSizes] [-addresses all | <classes-pattern>] [-noContent] pid | partial-executable-name | memory-graph-file DESCRIPTION
heap lists the objects currently allocated on the heap of the specified process, as well as summary data. Objects are categorized by class name, type (Objective-C, C++, or CFType), and binary image. C++ objects are identified by the vtable referenced from the start of the object, so with multiple inheritance this may not give the precise class of the object. The binary image identified for a class is the image which implements the class, not necessarily the binary image which caused the objects to be allocated at runtime, or which "owns" those objects. heap requires one argument -- either the process ID or the full or partial executable name of the process to examine, or the pathname of a memory graph file generated by leaks or the Xcode Memory Graph Debugger. The following options are available: -s | -sortBySize Sort output by total size of class instances, rather than by count. -z | -zones Show the output separated out into the different malloc zones, instead of an aggregated summary of all zones. -guessNonObjects Look through the memory contents of each Objective-C object to find pointers to malloc'ed blocks (non-objects), such as the variable array hanging from an NSArray. These referenced blocks of memory are identified as their offset from the start of the object (say "__NSCFArray[12]"). The count, number of bytes, and average size of memory blocks referenced from each different object offset loca- tion are listed in the output. -sumObjectFields Do the same analysis as with the -guessNonObjects option, but add the sizes of those referenced non-object fields into the entries for the corresponding objects. -showSizes Show the distribution of each malloc size for each object, instead of summing and averaging the sizes in a single entry. -addresses all | <classes-pattern> Print the addresses of all malloc blocks found on the heap in ascending address order, or the addresses of those objects whose full class name is matched by the regular expression <classes-pattern>. The string "all" indicates that the addresses of all blocks (both objects and non-objects) should be printed. The <classes-pattern> regular expression is interpreted as an extended (modern) regular expression as described by the re_format(7) manual page. Note that toll-free-bridged CoreFoundation and Foundation classes have the "__NSCF" prefix rather than just "NS" or "CF". Examples of valid classes-patterns include: __NSCFString 'NS.*' '__NSCFString|__NSCFArray' '.*(String|Array)' -noContent Do not show object content in -addresses mode. SEE ALSO
malloc(3), leaks(1), malloc_history(1), stringdups(1), vmmap(1), DevToolsSecurity(1) The Xcode developer tools also include Instruments, a graphical application that can give information similar to that provided by heap. The Allocations instrument graphically displays dynamic, real-time information about the object and memory use in an application, including back- traces of where the allocations occurred. The Leaks instrument performs memory leak analysis. BSD
April 26, 2018 BSD