LEAK in tsan racecheck_unittest tests on new win8 bot

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on June 20, 2013 12:14:09_

http://build.chromium.org/p/client.drmemory/builders/win-8_x64-drm/builds/9/steps/dbg%20full%20TSan%20tests/logs/summary%3A%201%20report%28s%29 Running ""..\tsan\unittest\bin\racecheck_unittest-windows-x86-O0.exe" "--gtest_filter="-PositiveTests.FreeVsRead:NegativeTests.WaitForMultiple*"" "-147""
Recorded 22 suppression(s) from user E:\b\build\slave\win-8_x64-drm\drmemory\tests\app_suite\default-suppressions.txt

Error `#1`: LEAK 44 direct bytes 0x0e674840-0x0e67486c + 44 indirect bytes
#0 replace_RtlAllocateHeap [e:\b\build\slave\win-8_x64-drm\drmemory\common\alloc_replace.c:2982]
#1 ntdll.dll!RtlCheckForOrphanedCriticalSections +0x2ee (0x777020dd )
#2 ntdll.dll!ApiSetQueryApiSetPresence +0xf1 (0x777544cb )
#3 ntdll.dll!LdrInitializeThunk +0xc9 (0x7774ab13 )
#4 ntdll.dll!LdrInitializeThunk +0x45 (0x7774aa8f )
#5 ntdll.dll!LdrInitializeThunk +0xf (0x7774aa59 )

Is this issue #385 w/o syms?

Same thing on tsan rel full and dbg full w/o syms.

On my own win8 vm I also see a leak w/ this callstack:

~~Dr.M~~ Error `#2`: LEAK 44 direct bytes 0x0e6d5d70-0x0e6d5d9c + 44 indirect bytes
~~Dr.M~~ # 0 replace_RtlAllocateHeap [c:\derek\drmemory\git\src\common\alloc_replace.c:2982]
~~Dr.M~~ # 1 ntdll.dll!LdrpGetNewTlsVector
~~Dr.M~~ # 2 ntdll.dll!LdrpInitializeThread
~~Dr.M~~ # 3 ntdll.dll!_LdrpInitialize
~~Dr.M~~ # 4 ntdll.dll!LdrpInitialize
~~Dr.M~~ # 5 ntdll.dll!LdrInitializeThunk

But ditto on my win7 machine! Yet the win7 bot doesn't show anything. Hmmm.

w/o syms on win8 VM:

Error `#2`: LEAK 44 direct bytes 0x0eee44a8-0x0eee44d4 + 44 indirect bytes
#0 replace_RtlAllocateHeap [c:\derek\drmemory\git\src\common\alloc_replace.c:2982]
#1 ntdll.dll!RtlGetCurrentDirectory_U +0x662 (0x77a4d7eb )
#2 ntdll.dll!RtlpMuiRegLoadRegistryInfo +0x14f3 (0x77a98efa )
#3 ntdll.dll!LdrInitializeThunk +0xc9 (0x77a8be9a )
#4 ntdll.dll!LdrInitializeThunk +0x45 (0x77a8be16 )
#5 ntdll.dll!LdrInitializeThunk +0xf (0x77a8bde0 )

More like issue #445 ?
A leak in LdrpGetNewTlsVector is in issue #1227 .

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=1279_