Possible leaks on Chromium printing_unittests

_From [timurrrr@google.com](https://code.google.com/u/timurrrr@google.com/) on August 29, 2011 11:41:56_

Windows 7 x64
[with PDB / without PDB]
POSSIBLE LEAK 88 direct bytes 0x0063bc48-0x0063bca0 + 32 indirect bytes
#1 AllocWrapper/? RPCRT4.dll+0x10636
#2 operator new/? RPCRT4.dll+0x10610
#3 LRPC_SASSOCIATION::FindOrCreateCausalFlow/RpcStringBindingParseW RPCRT4.dll+0x39984
#4 LRPC_SASSOCIATION::AddBinding/RpcStringBindingParseW RPCRT4.dll+0x39937
#5 LRPC_SASSOCIATION::HandleBindRequest/I_RpcInitFwImports RPCRT4.dll+0x3aa33
#6 LRPC_ADDRESS::HandleBindRequest/I_RpcInitFwImports RPCRT4.dll+0x3a9e6
#7 LRPC_ADDRESS::ProcessIO/I_RpcInitFwImports RPCRT4.dll+0x3a9b4
#8 LrpcServerIoHandler/I_RpcAsyncSetHandle RPCRT4.dll+0x348ec
#9 LrpcIoComplete/RpcMgmtSetCancelTimeout RPCRT4.dll+0x3474f
#10 TppAlpcpExecuteCallback/RtlDeleteAtomFromAtomTable ntdll.dll+0x64fde
#11 TppWorkerThread/TpSetTimer ntdll.dll+0x447f3
#12 BaseThreadInitThunk KERNEL32.dll+0x13677

POSSIBLE LEAK 196 direct bytes 0x0390d838-0x0390d8fc + 4148 indirect bytes
#1 AllocWrapper/? RPCRT4.dll+0x10636
#2 operator new/? RPCRT4.dll+0x10610
#3 ThreadSelfHelper/NdrNonEncapsulatedUnionMemorySize RPCRT4.dll+0x1dda3
#4 RpcpSetThreadpoolCallbackInstance/? RPCRT4.dll+0x10736
#5 LrpcIoComplete/RpcMgmtSetCancelTimeout RPCRT4.dll+0x34746
#6 TppAlpcpExecuteCallback/RtlDeleteAtomFromAtomTable ntdll.dll+0x64fde
#7 TppWorkerThread/TpSetTimer ntdll.dll+0x447f3
#8 BaseThreadInitThunk KERNEL32.dll+0x13677

---
Interestingly, I only see these reports when I run printing_unittests with the default --gtest_filter.
If I run it with EmfTest.FileBackedEmf excluded (xref issue #12 ), there are no reports at all.
If I run only EmfTest.FileBackedEmf, I can see only the leaks mentioned in issue #12 .

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