Mac Developer Library Developer


This manual page is for Mac OS X version 10.9

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

heap(1)                   BSD General Commands Manual                  heap(1)

     heap -- List all the malloc-allocated buffers in the process's heap

     heap [-guessNonObjects] [-sumObjectFields] [-showSizes] [-addresses all | <classes-pattern>]
          [-noContent] pid | partial-executable-name

     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 parameter -- either a process ID or a full or partial executable name.

     The following options are available:

             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 "__NSCFAr-ray[12]"). "__NSCFArray[12]").
             ray[12]").  The count, number of bytes, and average size of memory blocks referenced from each
             different object offset location are listed in the output.

             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.

             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) nonobjects)
             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-freed-bridged CoreFoundation and Foundation classes have the "__NSCF" prefix rather than
             just "NS" or "CF".  Examples of valid classes-patterns include:


             Do not show object content in -addresses mode.

     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 backtraces of where the allo-cations allocations
     cations occurred.  The Leaks instrument performs memory leak analysis.

BSD                              Mar. 16, 2013                             BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.