Issue 281613004: Don't let tcmalloc read all kinds of env vars at startup.

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

Issue 281613004: Don't let tcmalloc read all kinds of env vars at startup. (Closed)

Created:
6 years, 7 months ago by Nico

Modified:
6 years, 7 months ago

Reviewers:
willchan no longer on Chromium

CC:
chromium-reviews, dmikurube+memory_chromium.org

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

Don't let tcmalloc read all kinds of env vars at startup. The env vars are still used in profiling=1 builds, by such illustrious figures as the deep memory profiler bot and willchan. Reading from the environment variables uses static initializers, so this change will eliminate those static initializers in profiling=0 builds. As discussed in the chromium-dev thread "Does anyone use tcmalloc's debugging envvars?". BUG=94925 NOTRY=true Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=270850