From bruen...@google.com on September 12, 2012 12:35:39

I saw this in one app_suite pre-commit-suite run for release drmem:

Dr.M 2 unique, 2 total, 560 byte(s) of leak(s)

but I can't reproduce

leaks involving AllocWrapper have been seen in many places:
also seen on mspaint (xref issue #878 )
also seen on media_unittests (xref issue #454 )
also seen on unit_tests component build (not filed)
also seen on net_unittests ( issue #476 )
also seen on rpcrt4.dll!ThreadSelfHelper ( issue #751 )
also seen in printing_unittests ( issue #569 )
also seen in remoting_unittests ( issue #12 )

however it doesn't seem to add a header (xref issue #751) so these may not be
related to each other other than involving rpcrt4

Error #1: LEAK 32 direct bytes 0x00f9d100-0x00f9d120 + 40 indirect bytes
#0 RPCRT4.dll!AllocWrapper (0x76310636 <RPCRT4.dll+0x10636>)
??:0
#1 RPCRT4.dll!operator new (0x76310610 <RPCRT4.dll+0x10610>)
??:0
#2 RPCRT4.dll!DCE_BINDING::DuplicateDceBinding (0x76321c9f <RPCRT4.dll+0x21c9f>)
??:0
#3 RPCRT4.dll!LRPC_BINDING_HANDLE::CopyBindingHandleWithFailurePath (0x76321c55 <RPCRT4.dll+0x21c55>)
??:0
#4 RPCRT4.dll!LRPC_BASE_BINDING_HANDLE::BaseBindingCopy (0x7631b77b <RPCRT4.dll+0x1b77b>)
??:0
#5 RPCRT4.dll!LRPC_BINDING_HANDLE::BindingCopy (0x76321c1d <RPCRT4.dll+0x21c1d>)
??:0
#6 RPCRT4.dll!I_RpcBindingCopy (0x7631b98b <RPCRT4.dll+0x1b98b>)
??:0
#7 RPCRT4.dll!NDRCContextUnmarshallInternal (0x76318314 <RPCRT4.dll+0x18314>)
??:0
#8 RPCRT4.dll!NDRCContextUnmarshall2 (0x76318282 <RPCRT4.dll+0x18282>)
??:0
#9 RPCRT4.dll!NdrUnmarshallHandle (0x76318247 <RPCRT4.dll+0x18247>)
??:0
#10 RPCRT4.dll!NdrpClientUnMarshal (0x76317116 <RPCRT4.dll+0x17116>)
??:0
#11 RPCRT4.dll!_imp__OutputDebugStringA (0x763b015a <RPCRT4.dll+0xb015a>)
??:0

Error #2: LEAK 456 direct bytes 0x00f9f9a8-0x00f9fb70 + 32 indirect bytes
#0 RPCRT4.dll!AllocWrapper (0x76310636 <RPCRT4.dll+0x10636>)
??:0
#1 RPCRT4.dll!operator new (0x76310610 <RPCRT4.dll+0x10610>)
??:0
#2 RPCRT4.dll!LRPC_CASSOCIATION::AllocateCall (0x76321d68 <RPCRT4.dll+0x21d68>)
??:0
#3 RPCRT4.dll!LRPC_BINDING_HANDLE::NegotiateTransferSyntax (0x76321d15 <RPCRT4.dll+0x21d15>)
??:0
#4 RPCRT4.dll!I_RpcGetBufferWithObject (0x76317317 <RPCRT4.dll+0x17317>)
??:0
#5 RPCRT4.dll!I_RpcGetBuffer (0x763169fc <RPCRT4.dll+0x169fc>)
??:0
#6 RPCRT4.dll!NdrGetBuffer (0x76317f54 <RPCRT4.dll+0x17f54>)
??:0
#7 RPCRT4.dll!_imp__OutputDebugStringA (0x763b011d <RPCRT4.dll+0xb011d>)
??:0
#8 SspiCli.dll!? (0x749e363a <SspiCli.dll+0x2363a>)
??:0
#9 SspiCli.dll!SspipGetUserName (0x749d605c <SspiCli.dll+0x1605c>)
??:0
#10 SspiCli.dll!? (0x749da448 <SspiCli.dll+0x1a448>)
??:0
#11 SspiCli.dll!? (0x749da541 <SspiCli.dll+0x1a541>)
??:0

Original issue: http://code.google.com/p/drmemory/issues/detail?id=1023