Heap Profiling with MemoryInfra

As of Chrome 48, MemoryInfra supports heap profiling. Chrome will track all live allocations (calls to new or malloc without a subsequent call to delete or free) along with sufficient metadata to identify the code that made the allocation.

By default, MemoryInfra traces will not contain heap dumps. Heap profiling must be enabled viachrome://memory-internals orabout://flags.

How to obtain a heap dump (M66+, Linux, macOS, Windows)

1. Navigate tochrome://memory-internals.
   • There will be an error message at the top if heap-profiling is not supported on the current configuration
2. Enable heap profiling for the relevant processes. Future allocations will be tracked. Refresh the page to view tracked processes.
   • To enable tracking at process start, navigate tochrome://flags and search formemlog.
3. To take a heap dump, clicksave dump. This is stored as aMemoryInfra trace.
4. To symbolize the trace:

• Windows only: buildaddr2line-pdb from the chromium repository. For subsequent commands, add the flag--addr2line-executable=<path_to_addr2lin-pdb>
• If this is a local build, run the command./third_party/catapult/tracing/bin/symbolize_trace --is-local-build <path_to_trace>
• If this is an official Chrome build, run./third_party/catapult/tracing/bin/symbolize_trace <path_to_trace>. This will request authentication with google cloud storage to obtain symbol files [googlers only].
• If this is an official macOS or Linux Chrome build, add the flag--use-breakpad-symbols.
• If the trace is from a different device on the same operating system, add the flag--only-symbolize-chrome-symbols.
• If you run into the error “Nothing to symbolize” then backtraces are not working properly. There are two mechanisms that Chrome attempts to use: frame pointers if they're present, and backtrace lib. The former can be forced on with enable_frame_pointers gn arg. This should work on all architectures except for arm 32. The latter depends on unwind tables.

5. Load the (now symbolized) trace inchrome://tracing.

How to obtain a heap dump (M66+, Android)

On arm64 and x86-64, you can build chrome normally and follow steps above to obtain heap dumps.

To obtain native heap dumps on arm32, you will need a custom build of Chrome with the GN argumentsenable_profiling = true,arm_use_thumb = false,is_component_build = false andsymbol_level=1. All other steps are the same.

Alternatively, if you want to use an official build of Chrome, useis_official_build = true for arm32. If you want to use a released build, profiling only works on Dev and Canary on arm, and all channels on x86-64. In this case, you also need to fetch symbols manually and pass to the symbolize_trace script above.

How to obtain a heap dump (M65 and older)

For the most part, the settingenable-heap-profiling inchrome://flags has a similar effect to the variousmemlog flags.

How to manually browse a heap dump

1. Select a heavy memory dump indicated by a purple dot.

2. In the analysis view, cells marked with a triple bar icon (☰) contain heap dumps. Select such a cell.

   

3. Scroll down all the way toHeap Details.

4. To navigate allocations, select a frame in the right-side pane and press Enter/Return. To pop up the stack, press Backspace/Delete.

How to automatically extract large allocations from a heap dump

1. Runpython ./third_party/catapult/experimental/tracing/bin/diff_heap_profiler.py <path_to_trace>

2. This produces a directoryoutput, which contains a JSON file.

3. Load the contents of the JSON file in any JSON viewer, e.g.jsonviewer.

4. The JSON files shows allocations segmented by stacktrace, sorted by largest first.

Heap Details

The heap details view contains a tree that represents the heap. The size of the root node corresponds to the selected allocator cell.

The heap can be broken down in two ways: bybacktrace (marked with an ƒ), and bytype (marked with a Ⓣ). When tracing is enabled, Chrome records trace events, most of which appear in the flame chart in timeline view. At every point in time these trace events form a pseudo stack, and a vertical slice through the flame chart is like a backtrace. This corresponds to the ƒ nodes in the heap details view. Hence enabling more tracing categories will give a more detailed breakdown of the heap.

The other way to break down the heap is by object type. At the moment this is only supported for PartitionAlloc.

To keep the trace log small, uninteresting information is omitted from heap dumps. The long tail of small nodes is not dumped, but grouped in an<other> node instead. Note that although these small nodes are insignificant on their own, together they can be responsible for a significant portion of the heap. The<other> node is large in that case.

Example

In the trace below,ParseAuthorStyleSheet is called at some point.

The pseudo stack of trace events corresponds to the tree of ƒ nodes below. Of the 23.5 MiB of memory allocated with PartitionAlloc, 1.9 MiB was allocated insideParseAuthorStyleSheet, either directly, or at a deeper level (likeCSSParserImpl::parseStyleSheet).

By expandingParseAuthorStyleSheet, we can see which types were allocated there. Of the 1.9 MiB, 371 KiB was spent onImmutableStylePropertySets, and 238 KiB was spent onStringImpls.

It is also possible to break down by type first, and then by backtrace. Below we see that of the 23.5 MiB allocated with PartitionAlloc, 1 MiB is spent onNodes, and about half of the memory spent on nodes was allocated inHTMLDocumentParser.

Heap dump diffs are fully supported by trace viewer. Select a heavy memory dump (a purple dot), then with the control key select a heavy memory dump earlier in time. Below is a diff of theverge.com before and in the middle of loading ads. We can see that 4 MiB were allocated when parsing the documents in all those iframes, almost a megabyte of which was due to JavaScript. (Note that this is memory allocated by PartitionAlloc alone, the total renderer memory increase was around 72 MiB.)