[tcmalloc] remove remaining references to tcmalloc.
This is a follow-up to
https://chromium-review.googlesource.com/c/chromium/src/+/3402604.
Bug: 1257213, 973552, 98589
Change-Id: Ibee15fcf8b444e4d0c5db65a49d5f34fd8b78e05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3402350
Reviewed-by: Benoit Lize <[email protected]>
Reviewed-by: Nico Weber <[email protected]>
Reviewed-by: Dmitry Gozman <[email protected]>
Reviewed-by: Jamie Walch <[email protected]>
Commit-Queue: Thiabaud Engelbrecht <[email protected]>
Cr-Commit-Position: refs/heads/main@{#969727}
diff --git a/docs/linux/profiling.md b/docs/linux/profiling.md
index 4265909..029fb974 100644
--- a/docs/linux/profiling.md
+++ b/docs/linux/profiling.md
@@ -53,76 +53,16 @@
This will use the previously captured data (`perf.data`).
-### google-perftools
-
-google-perftools code is enabled when the `use_allocator` gn variable is set
-to `tcmalloc` (currently the default). That will build the tcmalloc library,
-including the cpu profiling and heap profiling code into Chromium. In order to
-get stacktraces in release builds on 64 bit, you will need to build with some
-extra flags enabled by setting `enable_profiling = true` in args.gn
-
-In order to enable cpu profiling, run Chromium with the environment variable
-`CPUPROFILE` set to a filename. For example:
-
- CPUPROFILE=/tmp/cpuprofile out/Release/chrome
-
-After the program exits successfully, the cpu profile will be available at the
-filename specified in the CPUPROFILE environment variable. You can then analyze
-it using the pprof script (distributed with google-perftools, installed by
-default on Googler Linux workstations). For example:
-
- pprof --gv out/Release/chrome /tmp/cpuprofile
-
-This will generate a visual representation of the cpu profile as a postscript
-file and load it up using `gv`. For more powerful commands, please refer to the
-pprof help output and the google-perftools documentation.
-
-Note that due to the current design of google-perftools' profiling tools, it is
-only possible to profile the browser process. You can also profile and pass the
-`--single-process` flag for a rough idea of what the render process looks like,
-but keep in mind that you'll be seeing a mixed browser/renderer codepath that is
-not used in production.
-
-For further information, please refer to
-http://google-perftools.googlecode.com/svn/trunk/doc/cpuprofile.html.
-
## Heap Profiling
-### google-perftools
-
-#### Turning on heap profiles
-
-Follow the instructions for enabling profiling as described above in the
-google-perftools section under CPU Profiling.
-
-To turn on the heap profiler on a Chromium build with tcmalloc, use the
-`HEAPPROFILE` environment variable to specify a filename for the heap profile.
-For example:
-
- HEAPPROFILE=/tmp/heapprofile out/Release/chrome
-
-After the program exits successfully, the heap profile will be available at the
-filename specified in the `HEAPPROFILE` environment variable.
-
-Some tests fork short-living processes which have a small memory footprint. To
-catch those, use the `HEAP_PROFILE_ALLOCATION_INTERVAL` environment variable.
-
#### Dumping a profile of a running process
-To programmatically generate a heap profile before exit, use code like:
-
- #include "third_party/tcmalloc/chromium/src/google/heap-profiler.h"
-
- // "foobar" will be included in the message printed to the console
- HeapProfilerDump("foobar");
-
-For example, you might hook that up to some action in the UI.
-
-Or you can use gdb to attach at any point:
+To programmatically generate a heap profile before exit, you can use gdb to
+attach at any point:
1. Attach gdb to the process: `$ gdb -p 12345`
-1. Cause it to dump a profile: `(gdb) p HeapProfilerDump("foobar")`
-1. The filename will be printed on the console you started Chrome from; e.g.
+2. Cause it to dump a profile: `(gdb) p HeapProfilerDump("foobar")`
+3. The filename will be printed on the console you started Chrome from; e.g.
"`Dumping heap profile to heap.0001.heap (foobar)`"
#### Analyzing dumps
@@ -145,12 +85,6 @@
Sandboxed renderer subprocesses will fail to write out heap profiling dumps. To
work around this, turn off the sandbox (via `export CHROME_DEVEL_SANDBOX=`).
-#### Troubleshooting
-
-* "Hooked allocator frame not found": build with `-Dcomponent=static_library`.
- `tcmalloc` gets confused when the allocator routines are in a different
- `.so` than the rest of the code.
-
#### More reading
For further information, please refer to
