third_party/tcmalloc/vendor/README - Issue 9701040: Revert 126715 - Update the tcmalloc vendor branch to r144 (gperftools 2.0).

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: third_party/tcmalloc/vendor/README

Issue 9701040: Revert 126715 - Update the tcmalloc vendor branch to r144 (gperftools 2.0). (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/

Patch Set: Created 8 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: third_party/tcmalloc/vendor/README

===================================================================

--- third_party/tcmalloc/vendor/README (revision 126727)

+++ third_party/tcmalloc/vendor/README (working copy)

@@ -23,9 +23,9 @@

own, built-in malloc; that assumption obviously isn't true with

tcmalloc. In practice, we haven't seen any problems with this, but

the expected risk is highest for users who register their own malloc

-hooks with tcmalloc (using gperftools/malloc_hook.h). The risk is

-lowest for folks who use tcmalloc_minimal (or, of course, who pass in

-the above flags :-) ).

+hooks with tcmalloc (using google/malloc_hook.h). The risk is lowest

+for folks who use tcmalloc_minimal (or, of course, who pass in the

+above flags :-) ).

HEAP PROFILER

@@ -227,7 +227,7 @@

workarounds.

Note that this only affects the cpu-profiler, which is a

-gperftools feature you must turn on manually by setting the

+google-perftools feature you must turn on manually by setting the

CPUPROFILE environment variable. If you do not turn on cpu-profiling,

you shouldn't see any crashes due to perftools.

« no previous file with comments | « third_party/tcmalloc/vendor/NEWS ('k') | third_party/tcmalloc/vendor/README_windows.txt » ('j') | no next file with comments »