chromium/src
0
Fork 0
Code Activity

[docs] Fix ToC and typo

Browse Source 
Follow-up to https://crrev.com/c/5377832.

Change-Id: I7bd935f2cdbd352d2ebe9ad65c0056ddc8334c36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5384027
Auto-Submit: Daniel Lehmann <dlehmann@chromium.org>
Reviewed-by: Benoit Lize <lizeb@chromium.org>
Commit-Queue: Benoit Lize <lizeb@chromium.org>
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1276135}
This commit is contained in:
Daniel Lehmann
2024-03-21 11:37:38 +00:00
committed by Chromium LUCI CQ
parent c85d4bdda3
commit 2cadc94e86
1 changed files with 3 additions and 3 deletions

6
docs/memory/heap_profiling_external.md

@@ -21,7 +21,7 @@ blindspots here](tools.md#heap-dumps).
[TOC] [TOC]
## <a name="heaptrack"></a> Using `heaptrack` ## <a name="heaptrack"></a> Using heaptrack
1. Build or install [heaptrack] and its GUI. 1. Build or install [heaptrack] and its GUI.
2. [Build Chrome](../get_the_code.md) with the following added to your 2. [Build Chrome](../get_the_code.md) with the following added to your
@@ -34,7 +34,7 @@ is_component_build = true # so that the allocation functions are dl-export
``` ```
Since [PartitionAlloc Everywhere](https://docs.google.com/document/d/1R1H9z5IVUAnXJgDjnts3nTJVcRbufWWT9ByXLgecSUM/preview), Since [PartitionAlloc Everywhere](https://docs.google.com/document/d/1R1H9z5IVUAnXJgDjnts3nTJVcRbufWWT9ByXLgecSUM/preview),
you should additionally disable PartitionAlloc and use the system allocator you should additionally disable PartitionAlloc and use the system allocator
instead, so that more allocations are captured in heaptrack. (Note that instead so that more allocations are captured in heaptrack. (Note that
PartitionAlloc is still used in Blink, just not for `malloc` in other places PartitionAlloc is still used in Blink, just not for `malloc` in other places
anymore.) Add these build flags additionally: anymore.) Add these build flags additionally:
``` ```
@@ -50,7 +50,7 @@ as `heaptrack.chrome.$pid.zst`. (Check the Chrome task manager for which tab
corresponds to which process ID.) corresponds to which process ID.)
4. Analyze the heap dump with `heaptrack --analyze heaptrack.chrome.$pid.zst`. 4. Analyze the heap dump with `heaptrack --analyze heaptrack.chrome.$pid.zst`.
## Using `tcmalloc` + `pprof` ## <a name="tcmalloc"></a> Using tcmalloc + pprof
Motivation: An alternative to heaptrack is to use the [heap Motivation: An alternative to heaptrack is to use the [heap
profiler](https://gperftools.github.io/gperftools/heapprofile.html) which is profiler](https://gperftools.github.io/gperftools/heapprofile.html) which is