title: Safest Way to Link Google's TCMalloc lib
body: <p>After some days of test I figured out that the runtime patching mechanism <a href="https://raw.githubusercontent.com/gperftools/gperftools/master/src/windows/patch_functions.cc" rel="nofollow">patch_functions.cc</a> is not safe to use in a production environment.
  <br>
  It seems to work well in a VS2010 project except for HeapAlloc() and HeapFree() but cannot be used in a VS2015 project due to some unresolved problems <a href="https://github.com/gperftools/gperftools/issues?utf8=%E2%9C%93&amp;q=is%3Aissue%20is%3Aopen%20VS2015" rel="nofollow">Open Issues</a>.
  the windows readme describes this alternative way to use tcmalloc:</p>
  
  <hr>
  
  <p><em>An alternative to all the above is to statically link your application
  with libc, and then replace its malloc with tcmalloc.  This allows you
  to just build and link your program normally; the tcmalloc support
  comes in a post-processing step.  This is more reliable than the above
  technique (which depends on run-time patching, which is inherently
  fragile), though more work to set up.  For details, see
     <a href="https://groups.google.com/group/google-perftools/browse_thread/thread/41cd3710af85e57b" rel="nofollow">https://groups.google.com/group/google-perftools/browse_thread/thread/41cd3710af85e57b</a></em></p>
  
  <hr>
  
  <p>Unfortunately the provided lik is urechable, seems that google had closed the group. <br><br>
  Could someone explain me how to do this?</p>