commit ef144fcccf0cdd09dd7d0c38b5a96b3ad6561a0f
author thakis@chromium.org <thakis@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> Thu May 15 23:24:17 2014
committer thakis@chromium.org <thakis@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> Thu May 15 23:24:17 2014
tree 797bf9dbe73a16d615c752188aca9ecc6f9fe289
parent 0c8e014b0b661e575f0dd6e1b8f6c83dacd7dbc7

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

Review URL: https://codereview.chromium.org/281613004

git-svn-id: http://src.chromium.org/svn/trunk/src/third_party/tcmalloc/chromium@270850 4ff67af0-8c30-449e-8e8b-ad334ec8d88c